Badee wrote on Sun, May 30, 2004 at 01:45:46AM -0700:
,----
| I wish to release my modified version of a GPL'ed program that I am
| using as an addon in my commerical app, but not my entire app. Here
| for an module i used GPL source code all other modules are developed
| by my own. The GPL modules is an addon module (It is not the part of
| base module).
|
| Being this the case i should disclose the whole source code or the Add
| on source code only.
|
| If i donot release the source code am i voilating GPL license?
`----
I'm assuming your commercial App isn't GPLed and that your module is a
library against which your commercial app is linked. Assuming my
assumptions are true, you are indeed violating GPL if you are planning
to link your non-GPLed app against a GPLed library. You either have to
GPL your commercial APP[1] or find an alternative module that is not
GPLed (preferably BSD or LGPLed).
Had this library been LGPLed and you made modifications to it, you
will still have the freedom of releasing only the modified version of
the library alone (not the oftware that links against your library).
Also, looking at it from the community perspective, The Free Software
Movement recommends programmers to release their libraries under GPL
and not LGPL. The readline[2] story is a pretty interesting thing to
read. But looking at it from the bread and butter perspective, its a
different thing altogether :)
-Suraj
References:
[1] http://www.panix.com/~kingdon/writings/bizmod.html
[2] http://www.gnu.org/licenses/why-not-lgpl.html
--
,-----------------[http://www.symonds.net/~suraj/]---o
| The linen bandages that were used to wrap Egyptian mummies averaged one
| thousand yards in length.
`------------------------------[suraj@xxxxxxxxxxx]---o
