[haiku-development] Re: INPUT / VOTE : --include-gpl-addons
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 21 Aug 2009 17:07:30 +0200 CEST
Urias McCullough <umccullough@xxxxxxxxx> wrote:
> On Fri, Aug 21, 2009 at 6:51 AM, Axel Dörfler<axeld@xxxxxxxxxxxxxxxx>
> wrote:
> > No, the writer of the add-on could not have chosen the GPL in the
> > first
> > place, since it's not applicable in this case (as he cannot force
> > the
> > LGPL or closed source OS parts to become GPL).
> > So if add-ons are to be handled like the FSF FAQ says, you cannot
> > create GPL add-ons for a non GPL piece of software (if the latter
> > should keep its license).
> > It all gets blurry a bit, though as the add-on creator could
> > release
> > the LGPLd OS as GPL, as those licenses are compatible :-)
> >
> > At least that's as far as I understood this mess...
> So, you're saying that it would essentially be impossible to create a
> hardware driver compiled for Windows that is licensed under GPL?
>
> Hmm... I could swear I've seen those before. Isn't that what the
> "System Libraries" exception is all about?
AFAICT yes, major system components are not affected by this.
> I am guessing it's perfectly fine as long as the add-on in question
> is
> a standalone "work" that is distributed by itself.
According to http://www.fsf.org/licensing/licenses/gpl-faq.html#GPLAndPlugins
"Can I apply the GPL when writing a plug-in for a non-free program?"
not, but I fail to read that out of the license text either.
Bye,
Axel.
Other related posts:
