-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/12/2013 05:30 PM, Christopher Head wrote:
> On Tue, 12 Feb 2013 20:51:15 +0000 (UTC)
> Duncan <1i5t5.dun...@cox.net> wrote:
> 
>> Christopher Head posted on Tue, 12 Feb 2013 11:38:14 -0800 as
>> excerpted:
>>
>>> On Sun, 10 Feb 2013 20:43:02 +0100 Dirkjan Ochtman <d...@gentoo.org>
>>> wrote:
>>>
>>>> On Sun, Feb 10, 2013 at 5:54 PM, Fabio Erculiani <lx...@gentoo.org>
>>>> wrote:
>>>>>> +1 from me; I've had a few machines break on kernel upgrades
>>>>>> because I didn't have the proper firmware installed (I guess
>>>>>> older kernel sources came with the firmware?).
>>
>>>>> For starters, if kernel sources provide /lib/firmware, how do you
>>>>> deal with file collisions?
>>>
>>> Please don't make kernel sources RDEPEND on firmware. The kernel
>>> DOES NOT depend on firmware to work properly. Well over half my
>>> machines prove that: they work perfectly fine (read: 100% of their
>>> hardware works) with no firmware at all installed.
>>
>> Not a problem as long as the RDEPEND is under USE=firmware or similar.
>> No USE=firmware, no rdepend!  =:^)
>>
>> Kernel sources providing /lib/firmware itself shouldn't be a problem 
>> either, as that's just a dir, which many packages may own.  The 
>> individual firmware files would be a problem, but the USE=firmware
>> RDEPEND solution should solve that.
>>
> 
> Yes, of course, I meant please don’t depend unconditionally. A
> conditional depend is fine by me, and I don’t care about one random
> directory being created—I just don’t want a whole package being pulled
> in for nothing.
> 
While much of this thread is un-actionable I believe this is a good idea
to do.

What is everyone's opinion of adding a USE=firmware option to pull in
PDEPEND="linux-firmware" in linux-2.eclass?

Thanks,
Zero

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRHyO1AAoJEKXdFCfdEflKV/UQAI3NTvDcGQs7hjzhkecIgxNh
11OLTv43CxLRUg4OeYJppeavxvV//LPIdroVUS2e7GgF3fQ++8HKa5s9xUzi7pmy
FoWgzoTG+IeTu7NF6MVMbyLO1hhH59+TEapBn4IFE4Da7qgK+3JrbF7Lx4cpxgnL
s7pJxQ2Fvm6x8Bz7NUwi4R1xnYKUJhEvxOJVCtWeChjr8c2u0zHahHnmAs9bdyeF
pnE4O7RD4I+lBUNI4kJGVM8EMK31LwFLgfyHkX8mPUyXQ9rA5+ofnxAHRIuV2zEA
g1f59f8b46VUy3mAJ296EXz//GZ+KxMtucAAwNLpEHEKoEj4Ypyb7rfQTlsSxUXu
kXVpB7bcDah5wT4i++UFpzzTx+wLVUxgOf/idRCUqDB8l2VqSSIqq6yJ+YA3eLoY
wCd9wEXR2sHaHxlwYvakMr0na3lAMIopPAM0t/0cwwIJYXlScYw6f5iEUDSo1if6
B+pUw7Hst4XsRWcQpzfjnR3tiKK9U7vTc58blz7pkkZo2cV/+PLlFzQf+WlPaxzU
ZRzcxoZnQFDifu/eXLQdVNzIfAuAzCYXiU2Rv3gowmwXlUuCQiyYcYUioCMRwFwt
7yPEXIGsMCX02sjLammF9ZM2RdyKjt/daKc1vMU29aMF/WB8T1nYUKVY/XZmJ+YR
YrDEf3MaIKbKoXXRuINy
=y/cz
-----END PGP SIGNATURE-----

Reply via email to