unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Kernel config
Date: Thu, 21 Jul 2016 14:06:50 +0200	[thread overview]
Message-ID: <87mvlbp545.fsf@gnu.org> (raw)
In-Reply-To: <CAEwRq=qCFni+pdcM2S9Qmue+3HUJNb5KG7E7S9mGYxFYjZ60sg@mail.gmail.com> (Vincent Legoll's message of "Wed, 20 Jul 2016 23:09:11 +0200")

Vincent Legoll <vincent.legoll@gmail.com> skribis:

>>   (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.
>
> Yep, inconvenient in the sense I couldn't find the right incantation to
> make this work, even with the help from people on #guix...

Here’s a more complete example that works for me.

First, I have this linux-libre.scm file in my GUIX_PACKAGE_PATH:

--8<---------------cut here---------------start------------->8---
(define-module (linux-libre)
  #:use-module (guix gexp)
  #:use-module (guix packages)
  #:use-module (gnu packages linux)
  #:use-module (srfi srfi-1))

(define-public my-own-linux-libre
  (package
    (inherit linux-libre)
    (name "linux-libre-for-myself")
    (native-inputs
     `(("kconfig" ,(local-file "./my-kernel.conf"))
       ,@(alist-delete "kconfig" (package-native-inputs linux-libre))))))
--8<---------------cut here---------------end--------------->8---

In the same directory lies the file ‘my-kernel.conf’.

With this, I can do:

--8<---------------cut here---------------start------------->8---
$ guix build linux-libre-for-myself -n --no-grafts
The following derivation would be built:
   /gnu/store/23b25z660ahglylv5blm2l9cbrc639c2-linux-libre-for-myself-4.6.4.drv
$ guix gc --references /gnu/store/23b25z660ahglylv5blm2l9cbrc639c2-linux-libre-for-myself-4.6.4.drv | grep my-kernel
/gnu/store/pq885cy0bi73acwh1wdx4agn5y5vrf2z-my-kernel.conf
$ cat /gnu/store/pq885cy0bi73acwh1wdx4agn5y5vrf2z-my-kernel.conf
Fake kernel conf.
--8<---------------cut here---------------end--------------->8---

Does something similar works for you?

HTH,
Ludo’.

  reply	other threads:[~2016-07-21 12:07 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
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 [this message]
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=87mvlbp545.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).