Re: Re: cvs: pear /PECL/smbc CREDITS IMPORTANT LICENSE Makefile.in config.m4 package.xml php_smbc.h smbc.c /PECL/smbc/tests 001.phpt 002.phpt

For a good reading on the reasons for this - have a look at the mozilla licence FAQ, and why it ended up as a tripple NPL/LGPL/GPL licence. Looks like the only 2 options for this would be. 1) not allowing gpl modules 2) doing the mozilla thing - triple licence -I can imagine that being a hot potato :) Other than that asking the Samba group to joint licence the smbclient code as LGPL/GPL..... Regards Alan Rasmus Lerdorf wrote:

There are GPL'ed PECL modules? Hrm, so there is. I don't think we can allow those. I am aware of the clause in the manual, but it was written mostly for the PEAR stuff. I did add a GPL warning in there a while ago. But the problem here is that the act of linking a GPL'ed library into both Apache and PHP violates the GPL. At least that is the view of the FSF. I don't really agree with that. You are correct that distributing the source code only through PEAR is not a direct violation, but I think we are splitting hairs as that code can not be used without violating the license. -Rasmus On Fri, 23 Aug 2002, Jelmer Vernooij wrote:

There are already GPL'ed modules in CVS and the pear site explicitly says that the GPL is allowed as a license. According to the GPL, it is allowed since the GPL'ed parts are added by 'phpize', which is part of the compile (and the compile tools may be proprieatry). The module may not be distributed along with non-gpled code (php headers and stuff) which is not the case at the mkoment. and it may also not be distributed in binary form. Downloading the sources and then running phpize locally over it should be allowed though. Jelmer On Thu, Aug 22, 2002 at 02:47:17PM -0700, Rasmus Lerdorf wrote about 'Re: [PEAR-CVS] cvs: pear /PECL/smbc CREDITS IMPORTANT LICENSE Makefile.in config.m4 package.xml php_smbc.h smbc.c /PECL/smbc/tests 001.phpt 002.phpt':

I don't know if we can accept this. The Apache/PHP license is not GPL compatible which means that it is a GPL violation to link libsmbclient into PHP. This extension does exactly that. For user-space PHP stuff in PEAR we can accept the GPL as a license, but I don't think we can for PECL stuff for this reason.

Unless someone can come up with some way around this, I'll have to ask you to put this somewhere else.

-Rasmus

On Thu, 22 Aug 2002, Jelmer Vernooij wrote:

ctrlsoft Thu Aug 22 17:44:33 2002 EDT

Added files: /pear/PECL/smbc CREDITS IMPORTANT LICENSE Makefile.in config.m4

                  	package.xml php_smbc.h smbc.c

/pear/PECL/smbc/tests 001.phpt 002.phpt Log:

Add SMB Client PEAR PECL module. Note that this code is GPL'ed (depends on GPL'ed libsmbclient).

-- Jelmer Vernooij <jelmer@nl.linux.org> - http://nl.linux.org/~jelmer/ Development And Underdevelopment: http://library.thinkquest.org/C0110231/ Listening to Error: The server (moosicd) doesn't seem to be running. 02:15:26 up 8 days, 40 min, 7 users, load average: 0.00, 0.00, 0.00