On Sat, Feb 05, 2005 at 05:13:51PM +0000, Edd Dumbill wrote: > On Sat, 2005-02-05 at 17:38 +0100, Bas Zoetekouw wrote: > > IMO the situation for this package is different from the kernel's. > > > > In the case of the kernel, it functions completely ok without any of > > the non-free firmwares; those only provide additional functionality. > > > > Bluez-bcm203x's only function otoh, is to load the non-free firmware. > > In this aspect, it is no different than a installer packages (flash, > > acroread, msttcorefonts, etc), and therefor should be in cntrib. > > The situation is slightly more subtle than that. bluez-bcm203x is part > of the same source package as bluez-utils, which are free software and > do provide a considerable amount of functionality. So moving the > bcm203x loader to contrib can't be done simply, as it would move all > Bluetooth basic support there.
Hmm, it is possible to only move one binary package to contrib and there are examples for this in the archive. I don't know if this is encouraged, though. > Also, by your argument all I'd have to do would be to move the firmware > loader program into bluez-utils rather than have it as a separate > package, and I'd satisfy your justification for the kernel not being in > contrib. Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
