1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 02/12/2013 05:30 PM, Christopher Head wrote: |
5 |
> On Tue, 12 Feb 2013 20:51:15 +0000 (UTC) |
6 |
> Duncan <1i5t5.duncan@×××.net> wrote: |
7 |
> |
8 |
>> Christopher Head posted on Tue, 12 Feb 2013 11:38:14 -0800 as |
9 |
>> excerpted: |
10 |
>> |
11 |
>>> On Sun, 10 Feb 2013 20:43:02 +0100 Dirkjan Ochtman <djc@g.o> |
12 |
>>> wrote: |
13 |
>>> |
14 |
>>>> On Sun, Feb 10, 2013 at 5:54 PM, Fabio Erculiani <lxnay@g.o> |
15 |
>>>> wrote: |
16 |
>>>>>> +1 from me; I've had a few machines break on kernel upgrades |
17 |
>>>>>> because I didn't have the proper firmware installed (I guess |
18 |
>>>>>> older kernel sources came with the firmware?). |
19 |
>> |
20 |
>>>>> For starters, if kernel sources provide /lib/firmware, how do you |
21 |
>>>>> deal with file collisions? |
22 |
>>> |
23 |
>>> Please don't make kernel sources RDEPEND on firmware. The kernel |
24 |
>>> DOES NOT depend on firmware to work properly. Well over half my |
25 |
>>> machines prove that: they work perfectly fine (read: 100% of their |
26 |
>>> hardware works) with no firmware at all installed. |
27 |
>> |
28 |
>> Not a problem as long as the RDEPEND is under USE=firmware or similar. |
29 |
>> No USE=firmware, no rdepend! =:^) |
30 |
>> |
31 |
>> Kernel sources providing /lib/firmware itself shouldn't be a problem |
32 |
>> either, as that's just a dir, which many packages may own. The |
33 |
>> individual firmware files would be a problem, but the USE=firmware |
34 |
>> RDEPEND solution should solve that. |
35 |
>> |
36 |
> |
37 |
> Yes, of course, I meant please don’t depend unconditionally. A |
38 |
> conditional depend is fine by me, and I don’t care about one random |
39 |
> directory being created—I just don’t want a whole package being pulled |
40 |
> in for nothing. |
41 |
> |
42 |
While much of this thread is un-actionable I believe this is a good idea |
43 |
to do. |
44 |
|
45 |
What is everyone's opinion of adding a USE=firmware option to pull in |
46 |
PDEPEND="linux-firmware" in linux-2.eclass? |
47 |
|
48 |
Thanks, |
49 |
Zero |
50 |
|
51 |
-----BEGIN PGP SIGNATURE----- |
52 |
Version: GnuPG v2.0.19 (GNU/Linux) |
53 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
54 |
|
55 |
iQIcBAEBAgAGBQJRHyO1AAoJEKXdFCfdEflKV/UQAI3NTvDcGQs7hjzhkecIgxNh |
56 |
11OLTv43CxLRUg4OeYJppeavxvV//LPIdroVUS2e7GgF3fQ++8HKa5s9xUzi7pmy |
57 |
FoWgzoTG+IeTu7NF6MVMbyLO1hhH59+TEapBn4IFE4Da7qgK+3JrbF7Lx4cpxgnL |
58 |
s7pJxQ2Fvm6x8Bz7NUwi4R1xnYKUJhEvxOJVCtWeChjr8c2u0zHahHnmAs9bdyeF |
59 |
pnE4O7RD4I+lBUNI4kJGVM8EMK31LwFLgfyHkX8mPUyXQ9rA5+ofnxAHRIuV2zEA |
60 |
g1f59f8b46VUy3mAJ296EXz//GZ+KxMtucAAwNLpEHEKoEj4Ypyb7rfQTlsSxUXu |
61 |
kXVpB7bcDah5wT4i++UFpzzTx+wLVUxgOf/idRCUqDB8l2VqSSIqq6yJ+YA3eLoY |
62 |
wCd9wEXR2sHaHxlwYvakMr0na3lAMIopPAM0t/0cwwIJYXlScYw6f5iEUDSo1if6 |
63 |
B+pUw7Hst4XsRWcQpzfjnR3tiKK9U7vTc58blz7pkkZo2cV/+PLlFzQf+WlPaxzU |
64 |
ZRzcxoZnQFDifu/eXLQdVNzIfAuAzCYXiU2Rv3gowmwXlUuCQiyYcYUioCMRwFwt |
65 |
7yPEXIGsMCX02sjLammF9ZM2RdyKjt/daKc1vMU29aMF/WB8T1nYUKVY/XZmJ+YR |
66 |
YrDEf3MaIKbKoXXRuINy |
67 |
=y/cz |
68 |
-----END PGP SIGNATURE----- |