From: "Ludovic Courtès" <ludo@gnu.org>
To: "Reza Alizadeh Majd" <r.majd@pantherx.org>
Cc: help-guix mailing list <help-guix@gnu.org>
Subject: Re: Access custom images inside disk image
Date: Tue, 26 May 2020 22:42:00 +0200 [thread overview]
Message-ID: <87h7w2o2cn.fsf@gnu.org> (raw)
In-Reply-To: <c7fa4396-39a0-4168-90bd-557e3a00a9ba@www.fastmail.com> (Reza Alizadeh Majd's message of "Tue, 19 May 2020 18:25:47 +0430")
Hello,
"Reza Alizadeh Majd" <r.majd@pantherx.org> skribis:
> I built a modified version of Guix to have a series of custom Channels
> by default. using this modified version, everything is OK, and I have
> access to these custom channels by default.
>
> The problem is that when I create a disk image using this custom build
> of Guix, only default Guix channel details is available during build,
> and I need to perform a `guix pull` to make the profile cache updated
> and install packages located in custom channels.
>
> is there any way that allow me to have these custom channels available
> by default in disk image?
To be clear, you don’t just want a predefined /etc/guix/channels.scm,
you want the actually channel bits as returned by ‘guix pull’, right?
This is currently not easy to do out of the box, but here’s a couple of
tricks to more or less do that:
https://git.savannah.gnu.org/cgit/guix/guix-artwork.git/tree/website/.guix.scm#n42
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/ci.scm#n265
The 2nd one in particular would allow you to treat a “pulled Guix” as a
package.
HTH!
Ludo’.
prev parent reply other threads:[~2020-05-26 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 13:55 Access custom images inside disk image Reza Alizadeh Majd
2020-05-21 5:30 ` Reza Alizadeh Majd
2020-05-26 20:42 ` Ludovic Courtès [this message]
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=87h7w2o2cn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=r.majd@pantherx.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.
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).