unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Elais Player <elais@fastmail.com>
To: phodina <phodina@protonmail.com>
Cc: help-guix@gnu.org
Subject: Re: How to add custom channels to ISO
Date: Fri, 30 Jul 2021 10:15:07 -0600	[thread overview]
Message-ID: <878s1naid0.fsf@fastmail.com> (raw)
In-Reply-To: <UDuED_rqSfbN-3OrnMs3J48k18XD9-U16_OJ2pHRoiZPeltj9w4U04EyWBLZHUXZXEpRDhEHMIjPnPmSE66q7GDOQtzn4S-FQ2gNQfh9TnM=@protonmail.com>


You could add the custom channels file as an 
=extra-special-file=[1] in the =os-configuration=.

It would look something like this:

#+BEGIN_SRC scheme
(define %my-installation-os
  (operating-system
    (inherit installation-os)
    (services
     (cons*
      (extra-special-file
        "/etc/guix/channels.scm"
        (local-file "/path/to/my/channels.scm"))
      (operating-system-services installation-os)))))
#+END_SRC

Plus side is you now have a global channels file from which all 
you need to do is run =guix pull= to have all your channels up to 
date. You may also want to pin those channels to certain commits 
just in case. Down side is running =guix pull= will start filling 
up your disk or memory on an ISO and you can easily run out of 
space. (I would advise not running =guix pull= until after 
partitioning and setting up the target system), and this file will 
be added to the store (but if you're creating a channels file in 
=/etc= shouldn't matter honestly).

phodina via <help-guix@gnu.org> writes:

> Hello,
>
> I'm migrating to a newer machine and I'm taking my GuixSD 
> configuration with me.
>
> So the first logical step I did was to create an ISO image based 
> on this section [1]. As I use my custom channel with modified 
> packages I added them to the configuration to make them 
> available on the new machine.
>
> Or so I thought. I booted and partitioned the new machine then 
> ran
> guix system init /root/configurations.scm /mnt to install Guix 
> there.
>
> However, after reboot turns out that the packages are not from 
> my channel but from public Guix repository without 
> modifications.
>
> Therefore my question is if it's possible to specify also 
> channels in the configuration file so that they are used during 
> installation?
>
> Reading the manual I came to a nice command guix system describe 
> [2] which gives me the current configuration with the 
> channels. Could that be used to build an ISO which would then 
> also know about the additional channels?
> Kind regards
> Petr
>
> [1]: 
> https://guix.gnu.org/manual/en/html_node/Building-the-Installation-Image.html
> [2]: 
> https://guix.gnu.org/manual/en/guix.html#Invoking-guix-describe


  reply	other threads:[~2021-07-30 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 16:00 How to add custom channels to ISO phodina via
2021-07-30 16:15 ` Elais Player [this message]
2021-08-03 20:12   ` phodina
2021-08-03 20:41     ` Elais Player

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=878s1naid0.fsf@fastmail.com \
    --to=elais@fastmail.com \
    --cc=help-guix@gnu.org \
    --cc=phodina@protonmail.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).