From: Raul Miller <moth@debian.org>
To: debian-legal@lists.debian.org, debian-kernel@lists.debian.org,
debian-devel@lists.debian.org, linux-kernel@vger.kernel.org
Subject: Re: How long is it acceptable to leave *undistributable* files in the kernel package?
Date: Fri, 18 Jun 2004 11:35:43 -0400 [thread overview]
Message-ID: <20040618113543.B1892@links.magenta.com> (raw)
In-Reply-To: <40D2F463.6090104@almg.gov.br>; from humberto.massa@almg.gov.br on Fri, Jun 18, 2004 at 10:55:47AM -0300
On Fri, Jun 18, 2004 at 10:55:47AM -0300, Humberto Massa wrote:
> What rights do the GPL'd software recipient have? The GPL grants
> some rights not granted by copyrights law. I made an extensive
> document and posted it to d-l, but no-one seemed to listen or to
> understand. All ok. IRT making derived works, the recipient has the
> right of making *some* derived works (respecting 2a and 2c) and to
> redistribute those derived works under the terms of the GPL itself.
> It seems not to permit anthology (collective) works, until you see
> the "mere aggregation" clause (section 2 third paragraph) /which/
> appears to cover anthology works.
That clause only deals with some anthology works, not all. It's an
exception to <<a "work based on the Program" means either the Program or
any derivative work under copyright law: that is to say, a work containing
the Program or a portion of it, either verbatim or with modifications...>>
It's pretty clear that the linux kernel is not a mere aggregation of
works on some volume of storage.
--
Raul
next prev parent reply other threads:[~2004-06-18 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <o0_liB.A.TFG.4fu0AB@murphy>
2004-06-18 13:55 ` Humberto Massa
2004-06-18 15:35 ` Raul Miller [this message]
2004-06-18 15:51 ` William Lee Irwin III
2004-06-18 16:50 ` Brian M. Carlson
2004-06-18 17:11 ` William Lee Irwin III
2004-06-19 0:12 ` David Schwartz
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=20040618113543.B1892@links.magenta.com \
--to=moth@debian.org \
--cc=debian-devel@lists.debian.org \
--cc=debian-kernel@lists.debian.org \
--cc=debian-legal@lists.debian.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome