From: Mike Frysinger <vapier@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 12:25:56 -0400 [thread overview]
Message-ID: <20150322162556.GP4504@vapier> (raw)
In-Reply-To: <21774.31608.991231.452934@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
On 22 Mar 2015 09:21, Ulrich Mueller 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.
no, content is licensed, not directories. you can't reasonably claim that all
the various files/ (like patches we grab from elsewhere) are all under GPL-2-
only.
> 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".
the combined work might be, but that doesn't mean the individual content itself
can't be different.
-mike</personal opinion>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-22 16:26 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
2015-03-22 16:22 ` Ulrich Mueller
2015-03-22 16:25 ` Mike Frysinger [this message]
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=20150322162556.GP4504@vapier \
--to=vapier@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