all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Marek Paśnikowski" <marek@marekpasnikowski.pl>
To: guix-devel@gnu.org
Subject: Re: The `channels' field of `operating-system' record
Date: Tue, 09 Apr 2024 06:16:12 +0200	[thread overview]
Message-ID: <6032424.lOV4Wx5bFT@akashi> (raw)
In-Reply-To: <CAEEhgEuMfkLACP6NLDtAASte2X7F5OZAm2HevVASu0_S6dG+dA@mail.gmail.com>

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

09.04.2024 06:06:00 CEST Nathan Dehnel:
> I don't think you're supposed to edit /etc/guix/channels.scm directly,
> I think it's generated by guix system reconfigure.
> https://gitlab.com/nonguix/nonguix/-/issues/33
> I have ~/.config/guix/channels.scm generated by putting
> home-channels-service-type in my guix home config.

Now that you mentioned it — is this not root user’s channel list, and
one is not supposed to use guix as root?

I use home-channels-service-type and the only issue with this solution
is that it requires a 'guix home reconfigure' before the new channels
can be used in 'guix pull'.  Though one could also use the -C flag to
a channels.scm file including the list of channels.

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

  reply	other threads:[~2024-04-09  9:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09  4:06 The `channels' field of `operating-system' record Nathan Dehnel
2024-04-09  4:16 ` Marek Paśnikowski [this message]
2024-04-09 12:28   ` Tomas Volf
2024-04-09 12:29 ` Tomas Volf
2024-04-09 12:33 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
  -- strict thread matches above, loose matches on Subject: below --
2024-04-07 16:05 Tomas Volf
2024-04-10 15:17 ` Ludovic Courtès
2024-04-15 22:04   ` Tomas Volf
2024-04-19 20:10     ` Ludovic Courtès
2024-05-08 23:16   ` Tomas Volf

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=6032424.lOV4Wx5bFT@akashi \
    --to=marek@marekpasnikowski.pl \
    --cc=guix-devel@gnu.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. 
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.