From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Watch out for license changes to GPL-3.
Date: Thu, 12 Jul 2007 21:12:15 +0100 [thread overview]
Message-ID: <20070712211215.66b62994@snowflake> (raw)
In-Reply-To: <1184270329.8615.13.camel@inertia.twi-31o2.org>
[-- Attachment #1: Type: text/plain, Size: 2518 bytes --]
On Thu, 12 Jul 2007 12:58:49 -0700
Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> > It would be an interesting question, though, to prove that someone
> > wrote a from-scratch ebuild via looking only at the documentation,
> > and without basing any parts off of already existing ebuilds in the
> > tree, no?
>
> How likely is this?
I know for a fact that people have already done it and are
redistributing works created that way without a Foundation copyright or
any "Based upon blah, which is copyright Gentoo blah" notice. I'm not
aware of any non-GPL-2 ebuilds being distributed, but if it is claimed
that all ebuilds are derived works of skel.ebuild then there's still a
copyright issue here.
> Let me put it another way. I write ebuilds all the time. I don't
> need to look at the documentation or any other ebuilds to write a new
> one. However, any ebuild I write is a derived work of previous
> ebuilds. Why? Because I used skel.ebuild and other ebuilds already
> in the tree as the basis for the ebuilds I originally wrote. Because
> I no longer need to actually *look* at other ebuilds doesn't change
> that my entire knowledge base for ebuild writing is derived from
> other ebuilds, which were based on other ebuilds before them.
Getting an idea or knowledge from somewhere doesn't subject something
to copyright or licence requirements. There may be patent and
non-disclosure issues, but neither are applicable here.
> Also, I would find it very difficult, if not impossible, to write an
> ebuild that is even slightly complex without using the eclasses, at
> all. Sure, it is *possible* that someone is capable of writing an
> ebuild entirely from scratch, but the likelihood is pretty much
> nonexistent.
As I understand it, merely using an eclass doesn't force GPL-2 on an
ebuild because there's no linkage involved.
> We could just end this really quickly and require all ebuilds
> submitted be done under GPLv2.
Sure, but what about third party ebuilds? Claiming that all ebuilds are
derived work of a Gentoo-copyrighted ebuild effectively requires all
ebuilds that don't have Gentoo copyright to include a statement like:
# Based upon skel.ebuild, which is Copyright 1999-2007 Gentoo Foundation
There are quite a few things out there that do not currently comply with
this requirement. If the Foundation truly believes that all ebuilds are
derived works, they should issue some kind of statement saying so.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-12 20:16 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 18:21 [gentoo-dev] app-arch/cpio-2.9 is now GPLv3 David
2007-07-07 18:35 ` [gentoo-dev] Watch out for license changes to GPL-3 Petteri Räty
2007-07-07 21:26 ` David
2007-07-08 10:28 ` [gentoo-dev] " Steve Long
2007-07-08 11:04 ` [gentoo-dev] " Marijn Schouten (hkBst)
2007-07-08 11:50 ` Wulf C. Krueger
2007-07-08 13:06 ` Seemant Kulleen
2007-07-08 14:46 ` Dominique Michel
2007-07-08 14:51 ` Ciaran McCreesh
2007-07-08 18:15 ` Harald van Dijk
2007-07-08 18:52 ` Wulf C. Krueger
2007-07-08 19:12 ` Harald van Dijk
2007-07-08 19:43 ` Wulf C. Krueger
2007-07-08 20:17 ` Harald van Dijk
2007-07-08 17:48 ` Seemant Kulleen
2007-07-08 18:15 ` Richard Freeman
2007-07-09 0:04 ` [gentoo-dev] " Duncan
2007-07-09 9:31 ` Steve Long
2007-07-09 15:13 ` Duncan
2007-07-09 16:27 ` Jeroen Roovers
2007-07-09 16:43 ` Petteri Räty
2007-07-09 19:37 ` Dominique Michel
2007-07-10 9:30 ` Duncan
[not found] ` <20070709163914.GB16617@kroah.com>
2007-07-09 19:07 ` [gentoo-dev] " Dominique Michel
2007-07-09 21:24 ` Greg KH
2007-07-10 17:10 ` Dominique Michel
2007-07-10 18:11 ` Greg KH
2007-07-10 20:37 ` Kevin Lacquement
2007-07-10 20:49 ` Greg KH
2007-07-12 9:18 ` [gentoo-dev] " Steve Long
2007-07-12 18:24 ` Chris Gianelloni
2007-07-12 18:31 ` Ciaran McCreesh
2007-07-12 19:00 ` Mike Frysinger
2007-07-12 19:07 ` Ciaran McCreesh
2007-07-12 19:14 ` Seemant Kulleen
2007-07-12 19:27 ` Ciaran McCreesh
2007-07-12 19:48 ` Wulf C. Krueger
2007-07-12 20:02 ` Ciaran McCreesh
2007-07-12 19:58 ` Chris Gianelloni
2007-07-12 20:12 ` Ciaran McCreesh [this message]
2007-07-12 20:17 ` Petteri Räty
2007-07-12 20:46 ` Harald van Dijk
2007-07-13 2:56 ` Jeroen Roovers
2007-07-12 20:10 ` Mike Frysinger
2007-07-12 20:16 ` Ciaran McCreesh
2007-07-12 21:06 ` Mike Frysinger
2007-07-12 21:11 ` Ciaran McCreesh
2007-07-12 21:32 ` Mike Frysinger
2007-07-13 2:53 ` Jeroen Roovers
2007-07-13 3:26 ` Mike Frysinger
2007-07-13 3:55 ` Marius Mauch
2007-07-13 4:20 ` Jeroen Roovers
2007-07-13 5:16 ` Mike Frysinger
2007-07-14 2:26 ` [gentoo-dev] " Steve Long
2007-07-12 22:33 ` Steve Long
2007-07-12 18:43 ` [gentoo-dev] " Greg KH
2007-07-12 22:56 ` [gentoo-dev] " Steve Long
2007-07-12 23:49 ` Greg KH
[not found] <4696b2bd.kcGnkUFoCMKDeiXx%Joerg.Schilling@fokus.fraunhofer.de>
2007-07-13 5:04 ` [gentoo-dev] " Harald van Dijk
2007-07-13 5:21 ` Harald van Dijk
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=20070712211215.66b62994@snowflake \
--to=ciaranm@ciaranm.org \
--cc=gentoo-dev@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