From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Loading modules built using linux-module-build-system
Date: Sun, 17 Nov 2019 21:35:32 +0100 [thread overview]
Message-ID: <87bltakzqj.fsf@gnu.org> (raw)
In-Reply-To: <20191114173143.6924e46e@scratchpost.org> (Danny Milosavljevic's message of "Thu, 14 Nov 2019 17:31:43 +0100")
Hello,
Danny Milosavljevic <dannym@scratchpost.org> 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’.
next prev parent reply other threads:[~2019-11-17 20:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 22:50 Loading modules built using linux-module-build-system Jelle Licht
2019-10-21 15:30 ` Jelle Licht
2019-10-21 18:27 ` Danny Milosavljevic
2019-10-21 18:49 ` Danny Milosavljevic
2019-10-21 21:39 ` Danny Milosavljevic
2019-10-22 12:24 ` Ludovic Courtès
2019-11-14 16:31 ` Danny Milosavljevic
2019-11-17 20:35 ` Ludovic Courtès [this message]
2019-12-22 20:06 ` Danny Milosavljevic
2019-12-30 18:55 ` Ludovic Courtès
2019-10-22 6:52 ` Giovanni Biscuolo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bltakzqj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.