Re: Proposal - Deferment of Changes from GR 2004-003
- To: Wouter Verhelst <wouter@grep.be>
- Cc: "Thomas Bushnell, BSG" <tb@becket.net>, Xavier Roche <roche@httrack.com>, debian-devel@lists.debian.org, debian-vote@lists.debian.org
- Subject: Re: Proposal - Deferment of Changes from GR 2004-003
- From: Andreas Barth <aba@not.so.argh.org>
- Date: Fri, 30 Apr 2004 10:40:53 +0200
- Message-id: <[🔎] 20040430084053.GA24917@mails.so.argh.org>
- Mail-followup-to: Andreas Barth <aba@not.so.argh.org>, Wouter Verhelst <wouter@grep.be>, "Thomas Bushnell, BSG" <tb@becket.net>, Xavier Roche <roche@httrack.com>, debian-devel@lists.debian.org, debian-vote@lists.debian.org
- In-reply-to: <[🔎] 20040430060827.GJ27955@grep.be>
- References: <[🔎] Pine.LNX.4.10.10404300655080.24425-100000@linux.localnet.loc> <[🔎] 8765bim4ul.fsf@becket.becket.net> <[🔎] 20040430060827.GJ27955@grep.be>
* Wouter Verhelst (wouter@grep.be) [040430 08:25]:
> On Thu, Apr 29, 2004 at 10:06:58PM -0700, Thomas Bushnell, BSG wrote:
> > I don't think this is right. If there is no dependency, the thing
> > doesn't have to be in contrib.
> >
> > Remember, a thing goes in contrib because it is only useful with
> > something in non-free. But a driver is useful for both the
> > proprietary firmware and any free firmware that should arise. Even
> > though the possibility of the latter is remote, I don't think it's so
> > remote that it means the thing should go in contrib.
> That doesn't matter. To date, the policy has always been that a package
> must go in contrib if it has a dependency on something in non-free which
> has no *current* free implementation. This makes a lot of sense; after
> all, non-free is just software, so you could theoretically rewrite
> everything in there, including libraries, firmware, and whatnot. If it
> were accepted that a hypothetically (though nonexisting) free
> implementation is enough to warrant moving a package from contrib to
> main, why should we still have contrib at all?
I don't seperate contrib and main via non-free. Just the other way:
Software in main needs to be DFSG-free, and also all dependencies must
be fulfiled in main (so that main is a closure).
There could be failures to fullfill this conditions in two ways:
Failing freeness, and failing the dependencies. That leads to:
free not free(*)
dependencies ok main non-free
dependencies failed contrib non-free
(with "free" is defined as "fulfills the DFSG", "not free" is defined
as "anything that is not free", "dependencies ok" is defined as "can
work with only software that actually is in main", and "dependencies
failed" is defined as "anything that is not dependencies ok".)
(*) actually, non-free falls into two categorys: distributable and not
legally distributable, and the second subcategory is not distributed
at all.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
Reply to: