1998-09-28 - Re: GPL & commercial software, the critical distinction (fwd)

Header Data

From: Jim Choate <ravage@EINSTEIN.ssz.com>
To: cypherpunks@EINSTEIN.ssz.com (Cypherpunks Distributed Remailer)
Message Hash: 504b06e3cc9408d3eb95b3c48c4f9ed804fe03f415baf4a1a1a9a41d2cffb2c6
Message ID: <199809290009.TAA03654@einstein.ssz.com>
Reply To: N/A
UTC Datetime: 1998-09-28 11:07:06 UTC
Raw Date: Mon, 28 Sep 1998 19:07:06 +0800

Raw message

From: Jim Choate <ravage@EINSTEIN.ssz.com>
Date: Mon, 28 Sep 1998 19:07:06 +0800
To: cypherpunks@EINSTEIN.ssz.com (Cypherpunks Distributed Remailer)
Subject: Re: GPL & commercial software, the critical distinction (fwd)
Message-ID: <199809290009.TAA03654@einstein.ssz.com>
MIME-Version: 1.0
Content-Type: text



Forwarded message:

> Date: Tue, 29 Sep 1998 00:45:55 +0100
> From: Adam Back <aba@dcs.ex.ac.uk>
> Subject: Re: GPL & commercial software, the critical distinction

> There are two distinct licenses promoted by the FSF.  They are the GNU
> GPL (General Public License) and the GNU LGPL (Library General Public
> License).
> 
> As you suggest the LGPL is usuable.

I'm suggesting both are usable for commercial code development, just don't
put GPL'ed source code in your source code. There is NO limitation of the
GPL or the LGPL that prevents a commercial product from making calls into
the GPL'ed library.

The problem with your interpretation is that in a sense you want your cake and
eat it too. In short you want to be able to use somebody elses code in your
product without their having a say in how their code is used or receiving a
cut of the profits. The GPL/LGPL is specificaly designed to prevent this.

If you use their code (not the binaries, though you will be required to
provide source to those binaries if you distribute it with your product
though this won't include the binaries to your commercial product) then
you must release your code - an extension of derivation.

If you desire to produce commercial secure-source code compatible with a GPL 
license then simply don't ship *any* GPL with your product and use no GPL
source or LGPL'ed library in source form in that product.

The point to the L/GPL is not to prevent commercial code development but
rather to prevent somebody from taking a library some programmer written and
released for non-commercial (a distinction not permited under public domain)
use while retaining control over that source so that if somebody, like
yourself, bops along and decides they can make a million with it the
original programmer gets a cut or you loose your million.

How does the original programmer get a cut? Simple, the commercial entity
contacts the programmer and licenses a non-GPL'ed version of the library.

Bottem line, don't steal other peoples code to make money without paying
them for their effort. It's that simple.


    ____________________________________________________________________

                            The seeker is a finder.

                                     Ancient Persian Proverb

       The Armadillo Group       ,::////;::-.          James Choate
       Austin, Tx               /:'///// ``::>/|/      ravage@ssz.com
       www.ssz.com            .',  ||||    `/( e\      512-451-7087
                           -====~~mm-'`-```-mm --'-
    --------------------------------------------------------------------





Thread