Re: Package proposal : TVision
| From: | Rasmus Lerdorf | Date: | Tue, 10 May 2005 08:28:58 +0000 |
| Subject: | Re: Package proposal : TVision | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-2351@lists.php.net to get a copy of this message | ||
Roman Neuhauser wrote:
> # demenev@gmail.com / 2005-05-10 17:12:49 +1100:
>
>>Here is the case:
>>
>>There is original code (O) that is in public domain, 2 forks - GPL'd
>>(G) and BSD'ish (B), and PHP extension (E) that can be linked to any
>>of G and B.
>>
>>The differences (affecting E) betwwen G and B are as follows:
>>
>>- different sets of defined constants
>>- minor differences in couple of data structures
>>- G adds some new functions, when linking to B, these functions are
>>implemented in E.
>>
>>The questions are:
>>
>>- is it safe from licensing POV to host E in PECL ?
>>- can I create a version of E that will use all range of G's
>>additional functionality and license it under GPL?
>>- if answer to prevous questions is yes, do I need a dul license for E?
>
>
> Would FSF answer such questions? They could perhpaps put these
> threads to an authoritative end. :)
RMS would just say No. We have had plenty of run-ins with him.
If you design the extension to make use of things only available in the
GPL'ed library, then by RMS's definition you are creating a derived work
and thus you have to GPL your extension. We can not host GPL'ed
extensions.
-Rasmus