[MonoDevelop] Licensing concerns.

Christoph Wille christophw@alphasierrapapa.com
Wed, 14 Jul 2004 07:27:18 +0200

At 12:42 AM 7/14/2004, John Luke wrote:
>On Tue, 13 Jul 2004 22:59:31 +0200, Christoph Wille
><christophw@alphasierrapapa.com> wrote:
> > If you take existing MIT code and stick it into a GPL application, fine. If
> > you extend a GPL application with newly written code that must rely on
> > infrastructure (short for assemblies and existing code) provided by GPLed
> > code, you cannot license that new code under MIT unless it does not contain
> > any linkage against GPLed code at the time you license it as MIT.
> >
>Unfortunately, I thought of another issue to respond to.  Using this
>logic, you would have to consider all AddIns to be derivative works.
>Is this your opinion, that it is not possible to write wholely
>independent AddIns for SharpDevelop or MonoDevelop unless they are
>also released under the GPL (even though there are none to my
>knowledge)?  Please say no, as I think that is a terribly limiting

Addins require to link against the infrastructure (core, services, you name 
it); the infrastructure is entirely GPL, not LPGL. As there is *no* linking 
exception in the #develop code base, yes, it is only possible to write GPL 
addins for #develop.