[Gllug] Can I link GNU AGPL code with GPL 2 code?

salsaman at xs4all.nl salsaman at xs4all.nl
Fri Feb 15 06:28:21 UTC 2008


On Fri, February 15, 2008 01:44, Justin Perreault wrote:
> On Thu, 2008-02-14 at 04:40 +0100, salsaman at xs4all.nl wrote:
>> On Wed, February 13, 2008 17:15, Progga wrote:
>> > On Wed, Feb 13, 2008 at 04:58:02PM +0100, salsaman at xs4all.nl wrote:
>> > Thanks!  I am going for it then :-)  It's relying on several PEAR
>> packages
>> > but
>> > PEAR uses the PHP license which sounds more like BSD sans advertising.
>>  So
>> > I
>> > hope that's okay as well.
>> >
>>
>> The PHP license might be problematic. The FSF license page says:
>>
>>  PHP License, Version 3.01
>>
>>     This license is used by most of PHP4. It is a non-copyleft free
>> software license. It is incompatible with the GNU GPL because it
>> includes strong restrictions on the use of "PHP" in the name of
>> derived products.
>>
>>     We recommend that you not use this license for anything except PHP
>> add-ons.
>
> If it is not incorporating the packages but just linking to them
> externally it is likely not an issue, but you would need to include both
> licenses when distributing if you ship the packages with. Then each
> license would be used applied to each part individually instead of on
> both together. iirc
>
> -Justin
>
> --
> Gllug mailing list  -  Gllug at gllug.org.uk
> http://lists.gllug.org.uk/mailman/listinfo/gllug
>
>

No, linking counts as a combined work. That is why binary Nvidia drivers
cannot be distributed with the Linux kernel, for example.

There seems to be some discussion of this here:
http://pear.php.net/manual/en/faq.devs.php

Gabriel.
http://lives.sf.net


-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug




More information about the GLLUG mailing list