On Wed, Mar 14, 2012 at 3:43 PM, Walter Dnes <waltd...@waltdnes.org> wrote: > On Wed, Mar 14, 2012 at 02:15:52PM +0100, J. Roeleveld wrote > >> Wouldn't a good solution be to have the ebuild modified to only >> install those binary blobs you actually need? Eg. similar to how >> apache or sane modules are configured? > > The tarball on the AMD website has all the binary blobs bundled > together. The ebuild simply downloads the tarball and extracts it to > the correct library directory. You could do it manually. The problem > with separate ebuilds is that one ebuild would be replaced with a couple > of dozen ebuilds, or one ebuild with a couple of dozen custom USE flags.
You could use an use-expand variable, like INPUT_DEVICES or VIDEO_CARDS for xorg-drivers, or DRACUT_MODULES for dracut. It sounds like the smart thing to do. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
