[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#727085: An HHVM-in-Debian State of the Union (was Re: Bug#727085: Taking over packaging in Debian.)



On 3/3/14, 2:01 PM, David Martínez Moreno wrote:
> On 2/28/14, 10:10 PM, László Böszörményi (GCS) wrote:
>> Hi Ender, all,
>>
>> On Fri, Feb 28, 2014 at 8:16 PM, David Martínez Moreno <ender@debian.org> wrote:
>>>         Hello all.  My name is Ender, I have been a Debian developer for quite some
>>> time and I work for Facebook, so I decided to do proper packaging of hhvm in
>>> Alioth, as having this done properly is a goal for the team in the first part of
>>> the year.

	Hello, I just wanted to update everyone on this thread with respect to the
Debian packaging.

	I have been working (with some help from Faidon) to bring the 2.4.1 tarball to
Debian standards.  The git repo (remember,
http://anonscm.debian.org/gitweb/?p=collab-maint/hhvm.git;a=summary) reflects
right now three major operational changes: integration of system's libzip,
integration of system's libsqlite3 and the removal of several libraries that
added useless dependencies to the package.

	Apart from that, the debian/copyright work is, as you may imagine, a three-ring
circus.  Apart from the huge list of contributors and different licenses, there
is a big showstopper that I found so far, which is that a couple of files are
licensed under the (in)famous JSON.org license (Software has to be used for Good
not Evil).  I'm doing my best to convince the in-house developers that switching
to pecl-json-c (from Remi Collet) is the best approach as we are not
bug-compatible anymore with the two main Linux families out there (Debian and
RedHat) since the end of May 2013, but at the same time they want to stay close
to PHP for good reasons.  There is an endless debate^W^W^Wmore information at
PHP#63520.

	In the meantime, Facebook has released HHVM 3.0.0 with Hack support (a superset
of PHP with gradual typing, collections and more stuff - http://hacklang.org).
While I'm all for packaging that version, I'm trying to stay close to 2.4.1 as I
already know my troubles with this version and I don't want to add more logs to
the fire, so I'm not updating the upstream version yet.  Also the 3.0.0 adds
dependencies like some OCaml code analysis tools depending on other stuff that
is not even nearly packaged, so...you know.

	All in all, the ball keeps rolling, and hopefully in another month or so I hope
to have a package ready in the archives.  Call me an optimist.

	Best regards,


		Ender.

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: