On Sun, 17 Feb 2013 12:42:11 +0100 Michał Górny <mgo...@gentoo.org> wrote:
> I would justify it through keeping things split and bit-exact clean, > instead of tightly integrated. > > Separate ebuilds mean that: > > - each firmware has proper license, > > - each firmware can be installed separately and it is _clean_ which > firmwares are actually installed (think of binpkgs), > > - each firmware can be upgraded when it needs to be (alternatively: all > firmwares are re-installed over and over again when new firmware is > added). > > And I wouldn't mind having even 200 sys-firmware/ packages. And don't > tell me that firmwares change every month, these are particularly > maintenance-free packages. > > And I don't mind having meta-packages for lazy people. > > Although I believe that having a few 'group' packages for firmwares > will be 'acceptable'. Assuming those firmwares share a common license. I very much agree with all of this. It would be nice if we could keep the individual firmware packages but just have them be a wrapper that depends on linux-firmware and ensures that the required files get installed (maybe by adding them to the savedconfig if it finds they aren't there). Yes, there are several problems with that idea, I know. -- gcc-porting toolchain, wxwidgets learn a language baby, it's that kind of place @ gentoo.org where low card is hunger and high card is taste
signature.asc
Description: PGP signature
