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
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 sam
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
license
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
conf
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
5 matches
Mail list logo
