[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Loading modules built using linux-module-build-system
From: |
Ludovic Courtès |
Subject: |
Re: Loading modules built using linux-module-build-system |
Date: |
Sun, 17 Nov 2019 21:35:32 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Hello,
Danny Milosavljevic <address@hidden> skribis:
>> Thinking more about it, what about handling the union/profile thing in
>> ‘operating-system-directory-base-entries’? We could still use
>> ‘profile-derivation’ with the hook you wrote, but we’d be able to keep
>> that here instead of adding it to (guix profiles).
>
> Should we just change out the "kernel" entry to be the union? After all,
> that's what actually happens at runtime as far as the Linux kernel is
> concerned.
Yes, that sounds good.
>> Also, if we take that route, we would probably need a
>> ‘linux-module-packages’ field in <operating-system>.
>
> Or make the `kernel` field a list, including linux-libre ;-)
Rather than a list, we could have a ‘make-linux-libre-union’ procedure
returning a <package>, so that we preserve consistent typing.
That is, people could write:
(kernel linux-libre)
or:
(kernel (make-linux-libre-union linux-libre some-package))
WDYT?
Thanks,
Ludo’.