From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org, 37868@debbugs.gnu.org
Subject: Re: Loading modules built using linux-module-build-system
Date: Mon, 30 Dec 2019 19:55:16 +0100 [thread overview]
Message-ID: <87sgl163u3.fsf@gnu.org> (raw)
In-Reply-To: <20191222210627.63fe1388@scratchpost.org> (Danny Milosavljevic's message of "Sun, 22 Dec 2019 21:06:27 +0100")
Hello,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Sun, 17 Nov 2019 21:35:32 +0100
> Ludovic Courtès <ludo@gnu.org> wrote:
>> 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?
>
> Hmm, isn't it more like a profile? I mean it would work the way above but
> there's (presumably) some reason why SOME-PACKAGE was an extra package.
You’re right, the union thing above is like a profile.
> We don't have to use the /run/current-system/profile for that, it could be
> a new one.
>
> What are the downside of using a profile vs. using a package in that way?
No downside to using a profile, as long as it’s not
/run/current-system/profile. The only remaining question is the
programming interface.
Possible options include ‘make-linux-libre-union’ above or a new
‘linux-module-packages’ field in <operating-system> as discussed at
<https://lists.gnu.org/archive/html/guix-devel/2019-10/msg00514.html>.
HTH,
Ludo’.
next prev parent reply other threads:[~2019-12-30 18:55 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
2019-12-22 20:06 ` Danny Milosavljevic
2019-12-30 18:55 ` Ludovic Courtès [this message]
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=87sgl163u3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37868@debbugs.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.