public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Bad license and attribution by ChromiumOS and CoreOS
Date: Sun, 22 Mar 2015 08:14:26 -0400	[thread overview]
Message-ID: <CAGfcS_kBZcoW7NW=SL1qf0OFnkrjwkdSiR5-2cqqCE6iZneB1A@mail.gmail.com> (raw)
In-Reply-To: <21774.31608.991231.452934@a1i15.kph.uni-mainz.de>

On Sun, Mar 22, 2015 at 4:21 AM, Ulrich Mueller <ulm@gentoo.org> wrote:
>>>>>> On Sun, 22 Mar 2015, Jeroen Roovers wrote:
>
>> Better yet, you can claim copyright on a "compilation" which is
>> probably what is effectively being done here. This is how people get
>> away with defending their copyright on publications of (slightly
>> modified/ abridged/ annotated, if at all) "compilations" of
>> centuries old works. Because copyright law.
>
> It doesn't work like this in our case. The Portage tree is licensed
> under the GPL-2. If someone takes a subset of ebuilds from it, it will
> be a "derivative work" and it cannot be distributed under any license
> other than the GPL-2.

That is true for the ebuilds that were copied/modified.  It isn't
necessarily true for other stuff stuck in the same tarball.

>
> It is even doubtful if any third-party ebuilds added to such a tree
> could be under a different license. If such ebuilds inherit from a GPL
> licensed eclass or depend on (or are depended on by) other ebuilds,
> they cannot "be reasonably considered independent and separate works
> in themselves".
>

That has been a longstanding argument with the GPL (you can link with
the LGPL under a non-free license, but not with the GPL).  However, it
has never actually been tested in court and I'm not convinced that it
will actually stand up.  The only content of the library/eclass/etc
that is present in the "derived work" are the names of symbols and the
name of the eclass and copyrighting those seems a lot like SCO arguing
that they can copyright signal enums.  They don't even get commingled
when you run the program - each gets loaded into its own set of memory
and the linker just fills in some memory addresses.

I'd think a judge would be as likely as not to say that the GPL would
only apply to the library itself, and that you could link whatever you
want to that library under any license at all, and that effectively
there is no distinction between the GPL and LGPL.  That is, if you get
the sort of judge who wouldn't give the win to SCO.

-- 
Rich


  reply	other threads:[~2015-03-22 12:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07  2:22 [gentoo-project] Bad license and attribution by ChromiumOS and CoreOS Patrick Lauer
2015-03-07  3:46 ` Alex Brandt
2015-03-07  3:55 ` Andrew Savchenko
2015-03-07  4:13   ` Rich Freeman
2015-03-07 13:44     ` Sven Vermeulen
2015-03-07  8:53 ` Ulrich Mueller
2015-03-07  9:05   ` Andrew Savchenko
2015-03-07 12:09   ` Rich Freeman
2015-03-07 14:27     ` Anthony G. Basile
2015-03-22  7:36       ` Jeroen Roovers
2015-03-22  8:21         ` Ulrich Mueller
2015-03-22 12:14           ` Rich Freeman [this message]
2015-03-22 16:22             ` Ulrich Mueller
2015-03-22 16:25           ` Mike Frysinger
2015-03-22 18:08             ` Ulrich Mueller
2015-03-11  6:11     ` Mike Frysinger
2015-03-07  9:33 ` Matthias Maier
2015-03-07 19:11 ` [gentoo-project] " Alec Warner
2015-03-11  5:22   ` Andrew Savchenko
2015-03-11  8:32     ` Kristian Fiskerstrand
2015-03-13  0:37   ` Alec Warner
2015-03-13  4:41 ` [gentoo-project] " Mike Frysinger
2015-03-13  7:46   ` Alexander Berntsen
2015-03-13 10:30   ` Andrew Savchenko
2015-03-13 11:26     ` Rich Freeman
2015-03-13 22:17       ` Rich Freeman
2015-03-13 22:29         ` Andrew Savchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGfcS_kBZcoW7NW=SL1qf0OFnkrjwkdSiR5-2cqqCE6iZneB1A@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox