From: Jelle Licht <jlicht@fsfe.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Liliana Marie Prikler" <liliana.prikler@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Using G-Expressions for public keys (substitutes and possibly more)
Date: Mon, 22 Nov 2021 15:32:03 +0100 [thread overview]
Message-ID: <864k84clcs.fsf@fsfe.org> (raw)
In-Reply-To: <87fsronwvg.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
>
>> I think we would probably want to improve on this end in the guile-
>> gcrypt module, i.e. have a public-key "constructor" that returns a
>> canonical-sexp and so on. WDYT?
>
> I don’t find it very compelling given there’s already
> ‘sexp->canonical-sexp’ & co. WDYT?
Well, the issue here is 'knowing' what sexp to pass along to that
function in the first place. Are Liliana & I missing something
obvious here?
I had to take a string representation of a valid canonical-sexp, and
pass it through string->canonical-sexp and canonical-sexp->sexp. It's
definitely not an issue for managing my local configuration, but it
seems silly to force _anyone_ wanting to write a canonical-sexp as a
sexp through this REPL adventure, for each kind of canonical-sexp.
- Jelle
next prev parent reply other threads:[~2021-11-22 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 12:47 Using G-Expressions for public keys (substitutes and possibly more) Liliana Marie Prikler
2021-10-21 20:13 ` Ludovic Courtès
2021-10-22 4:47 ` Liliana Marie Prikler
2021-11-21 0:12 ` Jelle Licht
2021-11-21 8:28 ` Liliana Marie Prikler
2021-11-22 13:27 ` Ludovic Courtès
2021-11-22 14:32 ` Jelle Licht [this message]
2021-11-22 19:35 ` Liliana Marie Prikler
2021-11-23 17:14 ` Ludovic Courtès
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=864k84clcs.fsf@fsfe.org \
--to=jlicht@fsfe.org \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
--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).