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. > 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. > > Here's the full parallel : > > > > The library is free, has no reverse depends in main, is thus only provided > > for the user to compile and use software coming outside of Debian. We > > can't assume anything about the software that the user will use. > > I disagree. We have to make assumptions about how software is normally > used to define reasonable values for dpkg headers like Depends: We're speaking of software of the user that is not packaged by us. I don't see how a dpkg Depends field is relevant here. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]