[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#353277: ndiswrapper in main



On Wed, Mar 01, 2006 at 01:22:22PM -0500, Raul Miller wrote:
> On 3/1/06, Raphael Hertzog <hertzog@debian.org> wrote:
> > On Wed, 01 Mar 2006, Raul Miller wrote:
> > > Let's grant that any "moving to contrib" will only happing in unstable/testing
> > > (and future stable) releases of debian.

> > > Do you see a problem with moving these to contrib?  After all, everything

> > Honestly I don't care enough about either those libs or ndiswrapper to
> > oppose to the move to contrib. But I've given my interpretation of the
> > policy and my rationale why they can/should be kept in main.

> > Now, you use that input how you want and you make up your own opinion.

> Ok, correct me if I'm wrong, here's how I'm understanding what you
> wrote: You feel that the contents of the "contrib" section mentioned in the
> social contract should be mechanically determined by debian package
> headers, and not by a more general concept of dependency?

> If that's not your point, I don't understand your input.

> > > in conjunction with non-free software.  Why do you think these other packages
> > > should not go in contrib?

> > Because they are DFSG-free, they have no explicit dependencies on a non-free
> > package and because they're not (installation) wrapper.

> It sounds to me like you're saying that all packages in contrib could
> be moved to main simply by removing the explicit dependencies in
> their package headers?

The lack of declared dependencies in ndiswrapper isn't a result of trying
to do an end-run around policy, it's a result of the fact that ndiswrapper
does not *have* a dependency on windows drivers in the sense that can
reasonably be represented in the Depends: field -- just as any given library
is of limited use on its own, yet it doesn't have an ORed dependency list on
all the packages (+ unpackaged software) that can use it.

Given that this is how we understand "dependency" every other time we use it
in the project, I think it would be inconsistent to say that ndiswrapper has
a "dependency" on an indeterminate but large number of distinct Windows
drivers.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature


Reply to: