From: ludo@gnu.org (Ludovic Courtès)
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Kernel config
Date: Sun, 17 Jul 2016 19:49:58 +0200 [thread overview]
Message-ID: <87zipg17eh.fsf@gnu.org> (raw)
In-Reply-To: <CAEwRq=rL82e-Mzhk87KAQi4cPAHcGTBO-Bh4T+pBUK=fqU+wuQ@mail.gmail.com> (Vincent Legoll's message of "Sun, 17 Jul 2016 18:22:12 +0200")
Vincent Legoll <vincent.legoll@gmail.com> skribis:
> Would the following work in the mean time ?
>
> 1. Adding the following to gnu/packages/linux.scm :
>
> (define-public linux-libre-config variant
> (package
> (inherit linux-libre)
> (native-inputs
> (let ((conf (kernel-config (or (%current-target-system)
> (%current-system))
> #:variant variant)))
> `(,@(alist-delete "kconfig" (package-native-inputs linux-libre))
> ("kconfig" ,conf))))))
This should roughly work. However, I think one can already provide
their own config file with something like:
(define-public my-own-linux-libre
(package
(inherit linux-libre)
(native-inputs
`(("kconfig" ,(local-file "./my-kernel.conf"))
,@(alist-delete "kconfig" (package-native-inputs linux-libre))))))
… which can be dropped in a file in $GUIX_PACKAGE_PATH.
It remains somewhat inconvenient, though.
WDYT?
Ludo’.
next prev parent reply other threads:[~2016-07-17 17:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 8:50 Kernel config Vincent Legoll
2016-07-16 13:23 ` Vincent Legoll
2016-07-16 17:39 ` Ricardo Wurmus
2016-07-16 18:25 ` Vincent Legoll
2016-07-16 20:44 ` Ludovic Courtès
2016-07-17 16:22 ` Vincent Legoll
2016-07-17 17:49 ` Ludovic Courtès [this message]
2016-07-17 18:51 ` Vincent Legoll
2016-07-17 18:59 ` Ricardo Wurmus
2016-07-20 21:09 ` Vincent Legoll
2016-07-21 12:06 ` Ludovic Courtès
2016-07-21 12:46 ` Vincent Legoll
2016-07-21 15:30 ` Ludovic Courtès
2016-07-21 18:47 ` Vincent Legoll
2016-07-22 8:22 ` Vincent Legoll
2016-07-22 8:28 ` Vincent Legoll
2016-07-22 12:44 ` Ludovic Courtès
2016-07-22 12:51 ` Vincent Legoll
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zipg17eh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=vincent.legoll@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).