From: Matt Turner <mattst88@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Last rites: sys-firmware/iwl6050-ucode
Date: Fri, 7 Feb 2020 11:50:13 -0800 [thread overview]
Message-ID: <CAEdQ38HLtiZ52fYd3FdLxPKTGa8RySkoGaaDEsExp68ajJOEcw@mail.gmail.com> (raw)
In-Reply-To: <uh802nq4y@kph.uni-mainz.de>
On Fri, Feb 7, 2020 at 11:39 AM Ulrich Mueller <ulm@gentoo.org> wrote:
>
> >>>>> On Fri, 07 Feb 2020, Matt Turner wrote:
>
> > On Fri, Feb 7, 2020 at 9:10 AM Mike Pagano <mpagano@gentoo.org> wrote:
> >>
> >> # Mike Pagano <mpagano@gentoo.org> (2020-02-07)
> >> # The standalone ebuild for this driver is made
> >> # unnecessary as it is included in the package:
> >> # sys-kernel/linux-firmware
> >> sys-firmware/iwl6050-ucode
>
> > How about all the others as well?
>
> > sys-firmware/iwl1000-ucode
> > sys-firmware/iwl3160-7260-bt-ucode
> > sys-firmware/iwl3160-ucode
> > sys-firmware/iwl6005-ucode
> > sys-firmware/iwl6030-ucode
> > sys-firmware/iwl7260-ucode
> > sys-firmware/iwl8000-ucode
>
> I had asked the same question back in November, but an argument against
> it was that sys-kernel/linux-firmware is quite a monster. In the default
> configuration, its installation footprint is 515 MiB.
Oh yeah. The thread where the person arguing for keeping them didn't
know about USE=savedconfig :)
next prev parent reply other threads:[~2020-02-07 19:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 17:10 [gentoo-dev] Last rites: sys-firmware/iwl6050-ucode Mike Pagano
2020-02-07 17:13 ` Mike Pagano
2020-02-07 17:55 ` Matt Turner
2020-02-07 19:39 ` Ulrich Mueller
2020-02-07 19:50 ` Matt Turner [this message]
2020-02-07 20:03 ` Michael 'veremitz' Everitt
2020-02-07 20:39 ` Matt Turner
2020-02-07 20:48 ` Michael 'veremitz' Everitt
2020-02-07 20:43 ` Alexander Tsoy
2020-02-07 21:43 ` Matt Turner
2020-02-07 20:47 ` Mike Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEdQ38HLtiZ52fYd3FdLxPKTGa8RySkoGaaDEsExp68ajJOEcw@mail.gmail.com \
--to=mattst88@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ulm@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox