Re: Package proposal : TVision
| From: | Roman Neuhauser | Date: | Mon, 09 May 2005 15:38:29 +0000 |
| Subject: | Re: Package proposal : TVision | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-2344@lists.php.net to get a copy of this message | ||
# demenev@gmail.com / 2005-04-26 23:29:25 +1100:
> 2005/4/26, Wez Furlong <kingwez@gmail.com>:
> > If the GPL library has the same API as the BSD licensed version, we
> > can safely link against the GPL'd version without being infected.
> >
> > Why? Because you can't impose the GPL on a public API that is not
> > already GPL'd.
> >
> > This trick is used for the readline extension, which links against the
> > BSD libedit as well as the GPL libreadline.
>
> The GPL'ed library's API can be considered a superset of the BSD one.
> It has some additional functions. Would it be acceptable in PECL to
> have code that uses these additional features?
(IANAL, but) this is what FSF says, and I read it as "no, it
wouldn't be acceptable":
http://www.fsf.org/licensing/licenses/gpl-faq.html#IfLibraryIsGPL
:
Q: If a library is released under the GPL (not the LGPL), does that
mean that any program which uses it has to be under the GPL?
A: Yes, because the program as it is actually run includes the library.
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991