[Ilugc] GPL
- From: joe_steeve@xxxxxxx (Joe Steeve)
- Date: Mon, 31 May 2004 06:25:44 +0530 (IST)
----Security_Multipart(Mon_May_31_06:25:44_2004_726)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Badee <gnubadee@xxxxxxxxx>
Date: Sun, 30 May 2004 01:45:46 -0700 (PDT)
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).
Check clause 2.a of the GNU GPL. It answers your question. If you
butcher a GPLed program and make a library out of it., I dont think
you can release it under LGPL. You still would have to release it in
GPL. (I may be wrong here.) Coz, if you could.. that would end up as a
loophole in the GNU GPL which could be used by non-cooperating people.
However the whole thing applies ONLY IF you plan to distribute your
app to the public. For example., if the app is going to be used only
in your company, you dont have to be bothered. If you are going to
sell you app to either the public or any one else.. then the license
should be GPL.
However, I dont accept your hesitation. You wanted to use GPLed code
to your benefits.. but not give back your code in return. This is not
a healthy attitude (IMO). That is like being a parasite.. you suck the
benefits out and leave the community when it is no more of any use to
you.
Cheers,
Joe
--
Free the code, free the user.
Homepage :
http://www.joesteeve.tk/
Web-log :
http://gnukid.blogspot.com/
----Security_Multipart(Mon_May_31_06:25:44_2004_726)--
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQBAuoKQykLM3FcsUXoRAiy8AJ4zoeDM8Ouk8uItyGcnWLYgjer0bwCeN7b+
ULxZVM/1qQehJOBuky+sZd0=
=t33x
-----END PGP SIGNATURE-----
----Security_Multipart(Mon_May_31_06:25:44_2004_726)----
Other related posts:
