Precedence: list
MIME-Version: 1.0
In-Reply-To: <ca6db022-fb04-6afc-a1b6-9bdd1c6e41ef@bitmessage.ch>
References: <4d19a51c-3eba-9775-0208-4d87da66effc@bitmessage.ch>
 <CA+T2pCEPW=1AM5RfypcbdNC+E8SnPXCBzRVM=QgE4NJ0-_uKbg@mail.gmail.com>
 <86963455-e88b-1014-4618-1a861257bb9f@bitmessage.ch> <20180109102454.4fb32aee@vostro>
 <ca6db022-fb04-6afc-a1b6-9bdd1c6e41ef@bitmessage.ch>
From: William Pitcock <nenolod@dereferenced.org>
Date: Tue, 9 Jan 2018 16:16:31 -0600
Message-ID: <CA+T2pCHnM7+jAAhak7VWGVfGGvHs=a8j6-f4fxN31pCf42VZqA@mail.gmail.com>
Subject: Re: [alpine-devel] Splitting up linux-firmware?
To: Oliver Smith <ollieparanoid@bitmessage.ch>
Cc: alpine-dev <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain; charset="UTF-8"

Hi,

On Tue, Jan 9, 2018 at 10:04 AM, Oliver Smith
<ollieparanoid@bitmessage.ch> wrote:
> I think it makes sense for the linux-* packages not to depend on the
> whole linux-firmware anymore, so people can really install only what they
> need. As Jirutka wrote on GitHub, it's probably a good idea to show a
> warning in post-upgrade, that most users need to install the subpackages
> (or simply the whole linux-firmware package) then.

I prefer to wait on removing the linux-firmware dependency until after
3.8 if possible.

> Regarding the modules I don't know if it's feasible to split them as well.

It should be possible to split by which module depends on what, but it
will be messy and require a significant rework of the package.
We could use modinfo to dump the firmware data for each module,
perhaps on kernel package build, and save that as a file somewhere
useful, perhaps in /lib/modules/$VERSION/firmwares.yaml or similar.

William


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---