FROM : p3consulting
DATE : Sat Apr 16 20:45:05 2005
Le 16 avr., 2005, à 20:11, Andy Satori a écrit :
> LGPL means you can link to it (dynamically), and ship it in binary
> form if you don't modify the source (or do, and release those changes
> back to the community) without also placing your code under the GPL.
> The GPL, which I gather the MySQL client libraries now use, doesn't
> even allow for that linking, if you incorporate GPL'd code in your
> project, it's license overrules that of the derived project, and you
> must release the changes and the derived code under the GPL.
>
> Unlike literary copyright, and plagiarism, it is not subject to the
> 10% change rule, a single GPL'd file in a 1000 file project is enough
> to invoke the GPL, and could be used to A) force the derived project
> to Open Source, or B) after an expensive legal battle, and a public
> relations black eye, remove the offending code and beg for
> forgiveness.
>
> Or C) pay the owners of the code obscene licensing fees.
>
>
Wrong:
the general rule is
"ask authorization to the owners to use their GPL/LGPL code under
others conditions"
to pay or not licensing fees is a product by product problem,
and to be correct a ( author ; product ; who ask ; for what usage )
problem.
assuming (obscene) licensing fees is - to say the least - misleading.
Pascal Pochet
<email_removed>
----------------------------------
PGP
KeyID: 0x208C5DBF
Fingerprint: 9BFB 245C 5BFE 7F1D 64B7 C473 ABB3 4E83 208C 5DBF
DATE : Sat Apr 16 20:45:05 2005
Le 16 avr., 2005, à 20:11, Andy Satori a écrit :
> LGPL means you can link to it (dynamically), and ship it in binary
> form if you don't modify the source (or do, and release those changes
> back to the community) without also placing your code under the GPL.
> The GPL, which I gather the MySQL client libraries now use, doesn't
> even allow for that linking, if you incorporate GPL'd code in your
> project, it's license overrules that of the derived project, and you
> must release the changes and the derived code under the GPL.
>
> Unlike literary copyright, and plagiarism, it is not subject to the
> 10% change rule, a single GPL'd file in a 1000 file project is enough
> to invoke the GPL, and could be used to A) force the derived project
> to Open Source, or B) after an expensive legal battle, and a public
> relations black eye, remove the offending code and beg for
> forgiveness.
>
> Or C) pay the owners of the code obscene licensing fees.
>
>
Wrong:
the general rule is
"ask authorization to the owners to use their GPL/LGPL code under
others conditions"
to pay or not licensing fees is a product by product problem,
and to be correct a ( author ; product ; who ask ; for what usage )
problem.
assuming (obscene) licensing fees is - to say the least - misleading.
Pascal Pochet
<email_removed>
----------------------------------
PGP
KeyID: 0x208C5DBF
Fingerprint: 9BFB 245C 5BFE 7F1D 64B7 C473 ABB3 4E83 208C 5DBF
| Related mails | Author | Date |
|---|---|---|
| Shreffler | Apr 15, 20:54 | |
| Mont Rothstein | Apr 15, 22:01 | |
| Philip Mötteli | Apr 16, 00:28 | |
| Ian was here | Apr 16, 09:14 | |
| Philip Mötteli | Apr 16, 11:53 | |
| Theodore Petrosky | Apr 16, 14:59 | |
| Andy Satori | Apr 16, 17:24 | |
| Philip Mötteli | Apr 16, 18:48 | |
| Andy Satori | Apr 16, 19:09 | |
| Philip Mötteli | Apr 16, 19:34 | |
| Andy Satori | Apr 16, 20:11 | |
| p3consulting | Apr 16, 20:45 | |
| The Karl Adam | Apr 16, 21:04 | |
| p3consulting | Apr 16, 21:44 | |
| mmalcolm crawford | Apr 16, 23:03 |






Cocoa mail archive

