| 1 |
On 07/02/20 19:50, Matt Turner wrote: |
| 2 |
> On Fri, Feb 7, 2020 at 11:39 AM Ulrich Mueller <ulm@g.o> wrote: |
| 3 |
>>>>>>> On Fri, 07 Feb 2020, Matt Turner wrote: |
| 4 |
>>> On Fri, Feb 7, 2020 at 9:10 AM Mike Pagano <mpagano@g.o> wrote: |
| 5 |
>>>> # Mike Pagano <mpagano@g.o> (2020-02-07) |
| 6 |
>>>> # The standalone ebuild for this driver is made |
| 7 |
>>>> # unnecessary as it is included in the package: |
| 8 |
>>>> # sys-kernel/linux-firmware |
| 9 |
>>>> sys-firmware/iwl6050-ucode |
| 10 |
>>> How about all the others as well? |
| 11 |
>>> sys-firmware/iwl1000-ucode |
| 12 |
>>> sys-firmware/iwl3160-7260-bt-ucode |
| 13 |
>>> sys-firmware/iwl3160-ucode |
| 14 |
>>> sys-firmware/iwl6005-ucode |
| 15 |
>>> sys-firmware/iwl6030-ucode |
| 16 |
>>> sys-firmware/iwl7260-ucode |
| 17 |
>>> sys-firmware/iwl8000-ucode |
| 18 |
>> I had asked the same question back in November, but an argument against |
| 19 |
>> it was that sys-kernel/linux-firmware is quite a monster. In the default |
| 20 |
>> configuration, its installation footprint is 515 MiB. |
| 21 |
> Oh yeah. The thread where the person arguing for keeping them didn't |
| 22 |
> know about USE=savedconfig :) |
| 23 |
> |
| 24 |
You still have to install the full 515MiB before you can apply savedconfig, |
| 25 |
unless you already know the list of firmwares included, and create the file |
| 26 |
in advance. For some systems (esp. storage constrained) that's not a very |
| 27 |
good option ... |
Archives