Mail archive

Re: [alpine-devel] APKBUILD for kernel modules

From: A. Wilcox <>
Date: Tue, 23 Jan 2018 17:36:33 -0600

On 01/23/18 13:34, Martin Galvan wrote:
> 2018-01-23 12:47 GMT-03:00 Mike Crute <>:
>> I built a kernel module package recently and there really aren't a lot
>> of good docs for this. As I understood the rationale for co-versioning
>> modules with the kernel it's about compatibility. A module is guaranteed
>> to be compatible with the kernel it's built against but not necessarily
>> against newer or older kernels, thus it doesn't make sense for the
>> module to maintain it's own version but rather to adopt the version of
>> the kernel it's built for.
> I understand. I thought a APK package would do something for me like
> packages generated by dkms-mkdeb do: give the module sources to the
> user, then rebuild the module in the target system for its running
> kernel.

If only.

> What it's not fully clear to me is how the module binaries are
> distributed. What if a user with an older kernel updates their aports
> tree, then tries to apk add a module package? How does the apk
> machinery know which binaries to provide?

I'm planning on fixing APK to handle kernel stuff better, because it's
pretty terrible right now; you can really wedge a system bad if you
upgrade the kernel package unknowingly (via `apk upgrade -qa` or such)
and then add a module package.


A. Wilcox (awilfox)
Project Lead, Adélie Linux

Received on Tue Jan 23 2018 - 17:36:33 UTC