From: "Brian M\. Carlson" <sandals@crustytoothpaste.ath.cx>
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 16:50:08 +0000 [thread overview]
Message-ID: <200406181650.34830.sandals@crustytoothpaste.ath.cx> (raw)
In-Reply-To: <20040618155113.GD1863@holomorphy.com>
-----BEGIN PGP SIGNED MESSAGE-----
On Friday 18 June 2004 15:51, William Lee Irwin III wrote:
> On Fri, Jun 18, 2004 at 11:35:43AM -0400, Raul Miller wrote:
> > 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.
>
> Any chance you guys could come to some kind of consensus on this so I
> know what has to be done for the debian package?
>
> Thanks.
If it's undistributable, it obviously doesn't belong in main. So please
remove the undistributable stuff. Second, if it's non-free, it doesn't
belong in the kernel, which is in main. So remove anything that is
non-free from the kernel-source. It's really not rocket science, and I
don't know why people insist upon talking about collective versus
derivative works, because none of this stuff belongs in main anyway.
If you need help in determining whether something is free or not, please send
a message to debian-legal (preferably in a new thread) asking that question.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iQEVAwUBQNMdSOWR/8lWBVPnAQFdPQf+P4lhAJpZ4Em1SByzalfDUQSkBvDoEM3a
YP7mAHV1i3cUWwVM0oWJnvOd2v9ZYmvDFk2VzXFh9SYz2wHnYGE0cs85jiKOtnjo
pItvmhry1/GZDQNVSHnAwX0hUl3K8VF8jWyOwXdYRYxlYYTmTd4tJYlaN9HTomhn
THCBCOF7ZY04qdoC4gslHVJAJm4CVBex6gfRz3O+ExkJC5TO5fT81D+vg+uQOs+N
ITGTI10ZjvmISTkYHaCRuTPwd6+S/AjPozoYzGyNOnVNoydX81VXIvHJtm+6mBuM
v/OmWflwUI0Y39Dm+NestF0HmIdjNMl7pm59V7PBXreldB02feibxQ==
=v2xr
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-18 16:51 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
2004-06-18 15:51 ` William Lee Irwin III
2004-06-18 16:50 ` Brian M. Carlson [this message]
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=200406181650.34830.sandals@crustytoothpaste.ath.cx \
--to=sandals@crustytoothpaste.ath.cx \
--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