On 5/11/22 03:48, Paul Wise wrote:
On Tue, 2022-05-10 at 14:30 -0600, Sam Hartman wrote:
So let's assume that at least all those packages can move to
non-free-firmware.
For backwards compatibility, I think that the firmware component is
going to need to be a subset of non-free; i.e. packages are going to
need to be *copied* not moved from non-free to the firmware component,
which means they would be available from both non-free components.
A work around would be to have some automation to check if non-free is
activated, and (propose to) update the sources.list automatically to add
non-free-firmware. I'd prefer doing this, as having copies of the same
package in both non-free and non-free-firmware is (IMO) a mess.
Cheers,
Thomas Goirand (zigo)