| 1 |
On Sat, Nov 16, 2019 at 9:08 AM Michael 'veremitz' Everitt |
| 2 |
<gentoo@×××××××.xyz> wrote: |
| 3 |
> |
| 4 |
> On 16/11/19 16:59, Matt Turner wrote: |
| 5 |
> > On Sat, Nov 16, 2019 at 1:06 AM Jaco Kroon <jaco@××××××.za> wrote: |
| 6 |
> >> Hi, |
| 7 |
> >> |
| 8 |
> >> On 2019/11/15 21:35, Matt Turner wrote: |
| 9 |
> >>> On Fri, Nov 15, 2019 at 2:20 AM Ulrich Mueller <ulm@g.o> wrote: |
| 10 |
> >>>> The package is somewhat redundant, because sys-kernel/linux-firmware |
| 11 |
> >>>> installs the same files. (Same for all other sys-firmware/iwl*-ucode |
| 12 |
> >>>> packages.) |
| 13 |
> >>> Should last-rite all of them, IMO. |
| 14 |
> >>> |
| 15 |
> >> I both agree and disagree with this. It's the simpler solution and |
| 16 |
> >> therefore I agree. |
| 17 |
> >> |
| 18 |
> >> I disagree because in some cases I really only want specific firmware |
| 19 |
> >> for specific sets of hardware (especially where space constraints are an |
| 20 |
> >> issue, read: embedded type systems). |
| 21 |
> >> |
| 22 |
> >> The current linux-firmware package is getting quite big in terms of install. |
| 23 |
> > USE=savedconfig allows you to choose exactly which files to install :) |
| 24 |
> > |
| 25 |
> I've never found a good way (yet...) to figure out how to write a fresh new |
| 26 |
> 'savedconfig' if you haven't ever previously emerged the package in |
| 27 |
> question. Does anyone have a good method for this, that doesn't require |
| 28 |
> unpacking the whole nine yards (Megs, Gigs...) first? |
| 29 |
|
| 30 |
You could look at the upstream git repo and make a list based on that. |
| 31 |
|
| 32 |
Or, since you have to download the tarball anyway, ebuild ... unpack |
| 33 |
it and inspect. |
| 34 |
|
| 35 |
Or, use the live ebuild to avoid downloading the same data multiple |
| 36 |
times per tarball. |
| 37 |
|
| 38 |
Or, if you want maximal bandwidth savings don't bother with any of |
| 39 |
this and install the files you want manually since the files aren't |
| 40 |
going to change. |
Archives