all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Marek Paśnikowski" <mail@marekpasnikowski.name>, 54711@debbugs.gnu.org
Subject: bug#54711: Bad Documentation Series: 6.1 Specifying Additional Channels
Date: Mon, 04 Apr 2022 21:47:30 +0200	[thread overview]
Message-ID: <2e3b78a8e94fb13bcf98ff8336a239b2e47040c3.camel@telenet.be> (raw)
In-Reply-To: <4b4fb5fcf67ee63c9899f43e9653b1cfd689dd26.camel@marekpasnikowski.name>

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

Marek Paśnikowski schreef op ma 04-04-2022 om 20:43 [+0200]:
> Regarding point 4.: I meant both /etc/config.scm and
> ~/src/guix-config/home-configuration.scm .
> My understanding is that it should be possible to define private
> (user specific) channels.
> I could be wrong here.
> I do not like the ~/.config/guix/channels.scm file,
> because it lives outside of the home configuration.

FWIW, you can create a symlink from ~/.config/guix/channels.scm to
~/src/guix-config/channels.scm and modify ~/src/guix-
config/channels.scm.  That way, the configuration files live together,
which might be close enough for your purposes.

> I would rather have it generated from the home config file.

You can define user-specific channels, in ~/.config/guix/channels.scm.
I suppose it might be technically possible to write a home
configuration that puts a file in ~/.config/guix/channels.scm and/or
runs the equivalent of "guix pull".

However, that's too late.  What you want is the home or system to be
reconfigured with a certain guix+channels Y mentioned in the home or
system configuration.  But when you run "guix system reconfigure", that
reconfiguration is performed with guix X.  While after the
reconfiguration, the guix is updated, the reconfiguration uses the old
guix.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-04-04 19:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 16:21 bug#54711: Bad Documentation Series: 6.1 Specifying Additional Channels Marek Paśnikowski
2022-04-04 17:53 ` Maxime Devos
2022-04-04 18:13   ` Maxime Devos
2022-04-04 17:55 ` Maxime Devos
2022-04-04 17:58 ` Maxime Devos
2022-04-04 18:02 ` Maxime Devos
2022-04-04 18:08 ` Maxime Devos
2022-04-04 18:43 ` Marek Paśnikowski
2022-04-04 19:47   ` Maxime Devos [this message]
2022-04-04 19:51   ` Maxime Devos
2022-04-04 19:52   ` Maxime Devos
2022-04-04 19:54   ` Maxime Devos
2022-04-10 12:55 ` Marek Paśnikowski
2022-04-10 13:33   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-04-10 13:54     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-04-10 16:27 ` Marek Paśnikowski

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=2e3b78a8e94fb13bcf98ff8336a239b2e47040c3.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54711@debbugs.gnu.org \
    --cc=mail@marekpasnikowski.name \
    /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.