Re: [ros-dev] [ros-diffs] [aandrejevic] 60485: [SOFT386] Change the license of Soft386 to GPLv2. The previous license was also GPLv2, but it had a runtime linking exception. The new license is the original GPLv2 with no exc...

[Aleksey Bragin]

You are implementing part of ReactOS so you can't just silently 
relicense your code in one commit to a license which is incompatible 
with ReactOS aims and goals.

At the very least, I would appreciate a discussion with our team 
regarding this before doing such commits.

Please revert. The runtime linking exception was added for a reason, not 
for amusement or RMS trolling. RMS is unhappy either way (not that I 
care about his opinion :).

Regards,
Aleksey Bragin

On 01.10.2013 2:01, aandrejevic(a)svn.reactos.org wrote:
>   Author: aandrejevic
>  Date: Mon Sep 30 22:01:38 2013
>  New Revision: 60485
>
>  URL: http://svn.reactos.org/svn/reactos?rev=60485&view=rev
>  Log:
>  [SOFT386]
>  Change the license of Soft386 to GPLv2. The previous license was also
>  GPLv2, but it had a runtime linking exception. The new license is the
>  original GPLv2 with no exceptions.
>
>
>  Added:
>       branches/ntvdm/lib/soft386/COPYING   (with props)
>  Modified:
>       branches/ntvdm/lib/soft386/common.c
>       branches/ntvdm/lib/soft386/common.h
>       branches/ntvdm/lib/soft386/common.inl
>       branches/ntvdm/lib/soft386/opcodes.c
>       branches/ntvdm/lib/soft386/opcodes.h
>       branches/ntvdm/lib/soft386/opgroups.c
>       branches/ntvdm/lib/soft386/opgroups.h
>       branches/ntvdm/lib/soft386/soft386.c
>

[Timo Kreuzer]

Did we ever care about this runtime linking exception stuff? We have
lots of GPL v2 3rd party code, does it all contain this clause?


Am 02.10.2013 10:47, schrieb Aleksey Bragin:
>   You are implementing part of ReactOS so you can't
> just silently
>  relicense your code in one commit to a license which is incompatible
>  with ReactOS aims and goals.
>
>  At the very least, I would appreciate a discussion with our team
>  regarding this before doing such commits.
>
>  Please revert. The runtime linking exception was added for a reason,
>  not for amusement or RMS trolling. RMS is unhappy either way (not that
>  I care about his opinion :).
>
>  Regards,
>  Aleksey Bragin
>
>  On 01.10.2013 2:01, aandrejevic(a)svn.reactos.org wrote:
> >   Author: aandrejevic
> >  Date: Mon Sep 30 22:01:38 2013
> >  New Revision: 60485
> >
> >  URL: http://svn.reactos.org/svn/reactos?rev=60485&view=rev
> >  Log:
> >  [SOFT386]
> >  Change the license of Soft386 to GPLv2. The previous license was also
> >  GPLv2, but it had a runtime linking exception. The new license is the
> >  original GPLv2 with no exceptions.
> >
> >
> >  Added:
> >       branches/ntvdm/lib/soft386/COPYING   (with props)
> >  Modified:
> >       branches/ntvdm/lib/soft386/common.c
> >       branches/ntvdm/lib/soft386/common.h
> >       branches/ntvdm/lib/soft386/common.inl
> >       branches/ntvdm/lib/soft386/opcodes.c
> >       branches/ntvdm/lib/soft386/opcodes.h
> >       branches/ntvdm/lib/soft386/opgroups.c
> >       branches/ntvdm/lib/soft386/opgroups.h
> >       branches/ntvdm/lib/soft386/soft386.c
> >  
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>

[Alexander Andrejevic]

I did talk about this on IRC with Thomas Faber and Ziliang Guo before changing
the license.
Also, it's worth to note that since most, if not all, of the 3rd party GPL code
is licensed under the regular GPL, that means the entire project is GPL, except
some modules have the runtime linking exception.
The linking exception makes sense for, say, ntoskrnl, to which drivers must link
to in order to compile, but allowing proprietary emulators to link to soft386
(which is just the library, not the entire ntvdm) is not something I'd prefer to
allow, even though it's unlikely since there are better emulators available.

Regards,
Aleksandar Andrejevic

On Wed, Oct 02, 2013 at 06:09:40PM +0200, Timo Kreuzer wrote:
>   
>  Did we ever care about this runtime linking exception stuff? We have
>  lots of GPL v2 3rd party code, does it all contain this clause?
>  
>  
>  Am 02.10.2013 10:47, schrieb Aleksey Bragin:
> >   You are implementing part of ReactOS so you
> > can't just silently
> >  relicense your code in one commit to a license which is incompatible
> >  with ReactOS aims and goals.
> >
> >  At the very least, I would appreciate a discussion with our team
> >  regarding this before doing such commits.
> >
> >  Please revert. The runtime linking exception was added for a reason,
> >  not for amusement or RMS trolling. RMS is unhappy either way (not that
> >  I care about his opinion :).
> >
> >  Regards,
> >  Aleksey Bragin
> >
> >  On 01.10.2013 2:01, aandrejevic(a)svn.reactos.org wrote:
> > >   Author: aandrejevic
> > >  Date: Mon Sep 30 22:01:38 2013
> > >  New Revision: 60485
> > >
> > >  URL: http://svn.reactos.org/svn/reactos?rev=60485&view=rev
> > >  Log:
> > >  [SOFT386]
> > >  Change the license of Soft386 to GPLv2. The previous license was also
> > >  GPLv2, but it had a runtime linking exception. The new license is the
> > >  original GPLv2 with no exceptions.
> > >
> > >
> > >  Added:
> > >       branches/ntvdm/lib/soft386/COPYING   (with props)
> > >  Modified:
> > >       branches/ntvdm/lib/soft386/common.c
> > >       branches/ntvdm/lib/soft386/common.h
> > >       branches/ntvdm/lib/soft386/common.inl
> > >       branches/ntvdm/lib/soft386/opcodes.c
> > >       branches/ntvdm/lib/soft386/opcodes.h
> > >       branches/ntvdm/lib/soft386/opgroups.c
> > >       branches/ntvdm/lib/soft386/opgroups.h
> > >       branches/ntvdm/lib/soft386/soft386.c
> > >  
> >
> >  _______________________________________________
> >  Ros-dev mailing list
> >  Ros-dev(a)reactos.org
> >  http://www.reactos.org/mailman/listinfo/ros-dev
> >  
>  
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev 
-- 
Alexander Andrejevic <theflash(a)sdf.lonestar.org>
SDF Public Access UNIX System - http://sdf.lonestar.org

[Colin Finck]

Aleksey Bragin <aleksey(a)reactos.org> wrote:
>   Please revert. The runtime linking exception was added
> for a reason, not
>  for amusement or RMS trolling. 
Isn't GPLv2 + "binary linking exception" = LGPLv2 anyway? I've never
fully understood our license, and therefore all my code is deliberately
licensed under "original" GPLv2 or later.


- Colin

[David Quintana (gigaherz)]

No, LGPL allows link-time merging of non-LGPL object files with LGPL
code, as long as you provide the object files necessary to reconstruct
the binary after changing the LGPL code.

On 2 October 2013 19:36, Colin Finck <colin(a)reactos.org> wrote:
>   Aleksey Bragin <aleksey(a)reactos.org> wrote:
> >   Please revert. The runtime linking exception was
> > added for a reason, not
> >  for amusement or RMS trolling. 
>  Isn't GPLv2 + "binary linking exception" = LGPLv2 anyway? I've never
>  fully understood our license, and therefore all my code is deliberately
>  licensed under "original" GPLv2 or later.
>
>
>  - Colin
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev