- From: arvindn@xxxxxxxxxxxxxxxxxxxxxxxxxx (Arvind Narayanan)
- Date: Mon, 31 May 2004 09:50:06 +0530
On Sun, May 30, 2004 at 01:45:46AM -0700, Badee wrote:
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?
It depends on the level of coupling between your app and your module.
If the module is a library that the app needs to compile and run, then
yes, you need to GPL the whole app. But if it is an "addon", as you say,
that can be dynamically loaded by your app at runtime, and the module
is *not* required for the base functionality of the app, then it is not
considered a derivative work. The relevant portion of the GPL is:
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
So, if I've understood your scenario correctly, then NO, you don't need
to GPL your whole app.
Q: Do you ever think about quantum computing?
Linus: I think that's a load of bull.
(From a Linux Lunacy cruise interview. After the presumptuous disparagement
of QC, Linus goes on to confuse it with DNA computing.)
Other related posts: