>> What else should I be doing to get this packaged up for inclusion in
>> debian?
> 
> Do you mean apart from persuading the copyright holder (Facebook, Inc.)
> to re-license hhvm under more general DFSG-free terms, such as the
> 3-clause BSD license?
> Your help in getting this issue solved would be highly appreciated, I
> think.
> Please re-read  http://bugs.debian.org/727085#60
> for further details on the licensing issue.

That rejection reason is pretty squarely aimed at people writing applications 
in the PHP language and makes sense for them. We are an alternative to php-src 
mostly coded in C++ and x86 assembly. (and after we prove ourselves I'll 
petition to be marked as an alternative for the php package).

As for the direct question. Much of our extension code was directly imported 
from php-src so we will absolutely be unable to relicense that portion. 
Untangling our contributions from the php-src ones is a very arduous task since 
there are many bug fixes to their code (some upstreamed, some not) as well as 
API changes and data structure replacements. We are happy with the php license 
so releasing the whole package under the same umbrella makes development much 
easier.

We are willing to relicense our portions under BSD but the technical splitting 
of the files into us vs them is just too much to ask.

Again, we are the first viable runtime alternative to php-src so I would argue 
that the rejection paragraph does not apply to us and didn't even consider us.

> I think László (who reads us in Cc) is still interested in packaging
> hhvm for inclusion in Debian.
> At least the bug is still an ITP bug and still owned by László, hence,
> unless he has just changed his mind, he should be still willing to work
> on the packaging...
> 
> I suggest you to get in touch with László and ask him whether and how
> you can help.

Laszlo, if you are listening out there please build us a package. You can see 
what I was doing at http://github.com/hhvm/packaging

> Thanks for being a Debian-friendly upstream developer and for offering
> to help!
> 
> Bye.
> 
> 
> -- 
> http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
> New GnuPG key, see the transition document!
> ..................................................... Francesco Poli .
> GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to