[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-licensing
Subject:    AW: Need help in licensing issue
From:       "Joseph WENNINGER" <jowenn () bigfoot ! com>
Date:       2000-07-13 6:36:14
[Download RAW message or body]

The plugins depend only on one headerfile and one cpp file. They only have
to implement a factory, but they don't touch the core.

Am I correct, If I use the QPL I can link my application against LGPL'ed
libraries, but no line of code my contain anything GPL'd code or may be
linked against some GPL'd library or kpart ?

Kind regards

Joseph WENNINGER



-----Ursprüngliche Nachricht-----
Von: forge@forge.kfs [mailto:forge@forge.kfs]Im Auftrag von Kevin Forge
Gesendet: Mittwoch, 12. Juli 2000 17:17
An: Joseph WENNINGER
Cc: kde-licensing@kde.org
Betreff: Re: Need help in licensing issue


Joseph WENNINGER wrote:
>
> Should I use LGPL for the plugin interface and publish the rest under GPL
or
> what's the best way?

Depending on how the plugin interface works this may be the logical
choice.  However if the integration runs to your application's core
you might want to put it all under the LGPL.  If on the other hand
the plugin integration is very loose and dynamic then the whole app
can be GPLed.

The wildcard license in this situation is the QPL under which QT-2.x
is distributed.  This provides a clear and simple solution for those
companies that wish to take your code proprietary for whatever reason.
You charge them money.

> Kind regards
> Joseph WENNINGER
> --
> Joseph WENNINGER
> jowenn@bigfoot.com        <<---- private
> wenning@ycom.at
> joseph.wenninger@chello.at
> business ----> j.wenninger@austroschrift.at

[prev in list] [next in list] [prev in thread] [next in thread]