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