unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: raingloom <raingloom@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 45911@debbugs.gnu.org
Subject: bug#45911: authorized-fields is not/badly documented
Date: Sat, 23 Jan 2021 06:39:03 +0100	[thread overview]
Message-ID: <20210123063903.66ad778c@riseup.net> (raw)
In-Reply-To: <87lfcof0xm.fsf@gnu.org>

On Wed, 20 Jan 2021 09:49:09 +0100
Ludovic Courtès <ludo@gnu.org> wrote:

> Hi,
> 
> raingloom <raingloom@riseup.net> skribis:
> 
> > I'm still confused about what the proper way to store the config
> > info is. Like how I should even store it as Scheme source code.  
> 
> Did you see this section and do you find it helpful?
> 
>   https://guix.gnu.org/manual/en/html_node/Getting-Substitutes-from-Other-Servers.html
> 
> Ludo’.

I have, that's how I found out where the setting even is.
An issue that I only now noticed is that it doesn't explain where to
obtain the signing key from, or the new behaviour of `guix archive
--authorize`.

If no one wants to fix it, I'll submit a patch once I'm done setting up
Snapper and some backups.

Edit after this sat in my queue for a few days:
Okay, so I figured out that I should use a G-Expression if I want to
compute the file, instead of just include it. Still not sure how to
store it as Scheme data, but I have an untested idea involving the
"pipe" syntax for symbols.

Thanks for the pointers!




  reply	other threads:[~2021-01-23  5:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16  3:16 bug#45911: authorized-fields is not/badly documented raingloom
2021-01-16  6:10 ` Ricardo Wurmus
2021-01-17  0:34   ` raingloom
2021-01-17  3:17     ` Julien Lepiller
2021-01-17  3:24     ` Julien Lepiller
2021-01-20 20:34       ` raingloom
2021-01-20 21:15         ` Julien Lepiller
2021-01-20  8:49     ` Ludovic Courtès
2021-01-23  5:39       ` raingloom [this message]
2021-01-23  9:10         ` Ricardo Wurmus
2021-01-25 17:15           ` raingloom
2021-01-26  7:13             ` Ricardo Wurmus

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=20210123063903.66ad778c@riseup.net \
    --to=raingloom@riseup.net \
    --cc=45911@debbugs.gnu.org \
    --cc=ludo@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).