Re: [PHP] Re: PHP License question
Yup. I believe that's what you have to do in order to satisfy the restrictions in the GPL. Gerard Samuel wrote: So to clarify. If I have a piece of code that utilises PEAR's Tar class (which uses a PHP License). In order for me to distribute my piece of code (under the GPL) along with the Tar class, I have to include this "exception" along with the normal GPL'ed notice in my code? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: PHP License question
On Friday 13 February 2004 01:27 pm, Ben Ramsey wrote: > > In addition, as a special exception, Ben Ramsey gives permission to link > the code of this program with those files in the PEAR library that are > licensed under the PHP License (or with modified versions of those files > that use the same license as those files), and distribute linked > combinations including the two. You must obey the GNU General Public > License in all respects for all of the code used other than those files > in the PEAR library that are licensed under the PHP License. If you > modify this file, you may extend this exception to your version of the > file, but you are not obligated to do so. If you do not wish to do so, > delete this exception statement from your version. > > > Since certain PEAR packages are licensed under the modified BSD and LGPL > licenses, then this exception does not need to be made for those > packages; these licenses are already GPL compatible. > > Thus, I can release my application under the GPL and satisfy its > requirements to include the PEAR packages licensed under the PHP license. > So to clarify. If I have a piece of code that utilises PEAR's Tar class (which uses a PHP License). In order for me to distribute my piece of code (under the GPL) along with the Tar class, I have to include this "exception" along with the normal GPL'ed notice in my code? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: PHP License question
I spoke with the good folks over at the FSF, and figured out how to do this. The PHP License itself does not restrict the use code under it. The problem was with the GPL, which restricted the use of code under the GPL being paired with code under certain types of licenses (specifically licenses that are non-copyleft). The PHP license is non-copyleft, and, so, it is not GPL compatible. Thus, an exception must be made by the copyright owner of the GPL'd code. The wording for the exception is found at http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs . Specifically, in this case, I chose to use the following wording, and the folks at FSF told me this was fine: In addition, as a special exception, Ben Ramsey gives permission to link the code of this program with those files in the PEAR library that are licensed under the PHP License (or with modified versions of those files that use the same license as those files), and distribute linked combinations including the two. You must obey the GNU General Public License in all respects for all of the code used other than those files in the PEAR library that are licensed under the PHP License. If you modify this file, you may extend this exception to your version of the file, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version. Since certain PEAR packages are licensed under the modified BSD and LGPL licenses, then this exception does not need to be made for those packages; these licenses are already GPL compatible. Thus, I can release my application under the GPL and satisfy its requirements to include the PEAR packages licensed under the PHP license. I hope this helps someone else out there, as well. ;-) -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: PHP License question
Ben, You can ship the package as two separately licensed components. The PEAR packages will retain their original licenses. If you customize the package, then you should redistribute it as a different thing under your own license, and probably rename the files/classes so that they don't confuse with the PEAR package. The only thing you cannot do is release the unomdified PEAR package under GPL. A better alternative is to use the LGPL, which does not force other packages to use GPL, but is still copy-left/open-source. Greg P.S. I'm not an expert, this is my common sense understanding of how the license works. The PHP License is less restrictive than GPL. You can do anything you want with the code as long as it doesn't affect the original code's license. Ben Ramsey wrote: I currently developing a project that I wish to release under a, preferably, open-source and "copy-left" license. So, I'm taking a close look at the GNU GPL for this, and it seems to serve this purpose, well. However, I am aware that the PHP license conflicts with the GNU GPL, and, thus, anything released under the PHP license cannot also be released in software under the GPL. At least, this is my assumption. Now, to my question: if a PEAR package is released under the PHP license, and my product is under the GPL, can I include the PEAR package in my product? Under the above assumption, the answer would be no. So, what license should I release my product under to maintain it's copy-left status and yet still allow the PEAR packages to be included? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: PHP License question
Ben Ramsey wrote: Now, to my question: if a PEAR package is released under the PHP license, and my product is under the GPL, can I include the PEAR package in my product? I don't know if this satisfies the legal requirement, but perhaps you could script some kind of automatic PEAR installation (assuming PEAR was already configured)? -Dan -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
