Re: Changing how we handle non-free firmware
On Fri, Aug 19, 2022 at 11:26:51AM +0100, Steve McIntyre wrote:
> Hey Wouter!
>
> On Fri, Aug 19, 2022 at 12:19:55PM +0200, Wouter Verhelst wrote:
> >On Thu, Aug 18, 2022 at 08:58:21PM +0100, Steve McIntyre wrote:
> >> system will *also* be configured to use the non-free-firmware
> >> component by default in the apt sources.list file.
> >
> >What's the rationale for this one?
> >
> >I think it would make more sense to only configure the system to enable
> >the non-free-firmware component if the installer determines that
> >packages from that component are useful for the running system (or if
> >the user explicitly asked to do so).
>
> That's a fair point, my text was unclear here. Let's tweak it:
>
> "Where non-free firmware is found to be necessary, the target system
> will *also* be configured to use the non-free-firmware component by
> default in the apt sources.list file."
>
> Does that sound better?
Much!
With that tweak, I would second it, except that I am out of a GPG key
currently.
> >If I'm not mistaken, code to do this already exists, and seems to work
> >well (but do correct me if I'm wrong).
>
> Ish! :-)
>
> We don't have any code in d-i to deal with the *non-free-firmware*
> component yet, but I#m sure we can adapt the existing stuff around
> non-free / contrib to suit.
Well, yes, that's what I meant.
--
w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}
I will have a Tin-Actinium-Potassium mixture, thanks.
Reply to: