Re: [TCLUG:17805] Licensing (was: Re: [TCLUG:17728] Motif has gone opensource!)

["Thomas T. Veldhouse" <veldy@veldy.net>]

What about LGPL?  You can link that into commercial software.  No problem.

Tom Veldhouse
veldy@veldy.net

----- Original Message -----
From: "Mike Hicks" <hick0088@tc.umn.edu>
To: <tclug-list@mn-linux.org>
Sent: Wednesday, May 17, 2000 4:35 PM
Subject: [TCLUG:17805] Licensing (was: Re: [TCLUG:17728] Motif has gone
opensource!)


> "Schlough, Mark" wrote:
> >
> >         I don't know this but I'm just asking....
> >
> >         Could a company write a proprietary program that uses GPL'd code
in
> > this way:
> >         There are proprietary components and GPL'd components.  The
> > proprietary stuff is distributed in one tarball and the GPL'd in
another.
> > And the install program assembles them into a hybrid system.  (Sort of
like
> > bricks and mortar... Proprietary Bricks and GPL'd mortar...together they
> > make the structure)
>
> You could probably do this if you actually had two separate programs
> that communicated closely through shared memory or something, but you
> aren't supposed to be able to link GPLed code into a proprietary
> program.  However, you can link proprietary code into an otherwise GPLed
> program, IIRC.  There are many GPLed programs that use Motif for a
> widget toolkit, for example.  The Gimp used to use Motif as its widget
> toolkit, but the developers decided to attempt to move away from Motif,
> and GTK (a.k.a. The Gimp Toolkit) was born.
>
> At any rate, you might be able to pull it off, though you would have
> much better luck mixing LGPL and proprietary code rather than
> GPL/proprietary.
>
> --
>  _  _  _  _ _  ___    _ _  _  ___ _ _  __   #define SIGNUKE
> / \/ \(_)| ' // ._\  / - \(_)/ ./| ' /(__   /* Nuclear event occured */
> \_||_/|_||_|_\\___/  \_-_/|_|\__\|_|_\ __)
> [ Mike Hicks | http://umn.edu/~hick0088/ | mailto:hick0088@tc.umn.edu ]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> For additional commands, e-mail: tclug-list-help@mn-linux.org
>
>