From: Maxime Devos <maximedevos@telenet.be>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>,
guile-devel <guile-devel@gnu.org>
Subject: Re: (ice-9 base64)?
Date: Tue, 16 Aug 2022 18:58:59 +0200 [thread overview]
Message-ID: <33556713-c85b-ab0f-554e-94a40f9d418e@telenet.be> (raw)
In-Reply-To: <CA+XASoUx+D059h-Df-qQfkmvXto9YEbB25PENqF104NnbzdCNg@mail.gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1493 bytes --]
On 16-08-2022 18:10, Aleix Conchillo Flaqué wrote:
> Hi,
>
> In many projects I've been copying Göran Weinholt's base64
> implementation and I've also seen it in other projects, would it make
> sense to include it in Guile's standard library? [...]
If we do this, we should contact the various other projects to make them
use (ice-9 base64).
I think it would be simpler though to consider the base64 in
guile-gcrypt to be 'canonical', it would avoid problems with old
versions of Guile not having the base64 module and newer version having
it, which would prevent using the proposed (ice-9 base64) in Guile
because it would break build-aux/build-self.scm when pulling or
time-machining from old Guix that have an old Guile.
Whether we simply replace (guix base64) by (gcrypt base64) depends on
how old (gcrypt base64) is compared to the earliest 'supported' Guix for
pull/time-travel, but even if it is not present in the old gcrypt, we
can work-around that (we have a 'fake-gcrypt-hash' in
build-aux/build-self.scm, so we can easily have a (define gcrypt-base64
[some copy])). Or simply update the local guile-gcrypt in
buid-aux/build-self.scm.
OTOH a similar replacement can be done for (ice-9 base64), but
transitioning to (ice-9 base64) would take much longer, at least until
the various distributions are updated to a Guile that has (ice-9
base64), whereas (gcrypt base64) could be switched to immediately.
Greetings,
Maxime.
[-- Attachment #1.1.1.2: Type: text/html, Size: 2318 bytes --]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-08-16 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 16:10 (ice-9 base64)? Aleix Conchillo Flaqué
2022-08-16 16:16 ` [EXT] " Thompson, David
2022-08-16 16:58 ` Maxime Devos [this message]
2022-08-16 17:21 ` Aleix Conchillo Flaqué
[not found] ` <df5ce89f-a7a2-7337-8dc7-67372cb1c48c@telenet.be>
[not found] ` <CA+XASoWyG7xDNcRyX46RERoORB=a=hckh5uU3MQvJ-z8ou-9Fg@mail.gmail.com>
[not found] ` <5331d2f3-13a5-e40c-f3bb-398438a0b103@telenet.be>
[not found] ` <CA+XASoXPLroB1LLb6yi4w0nAd20xHGC0HBEJtjUYzuFP7XCAWw@mail.gmail.com>
2022-08-18 7:56 ` Maxime Devos
2022-08-19 0:20 ` Aleix Conchillo Flaqué
2022-08-19 10:06 ` Maxime Devos
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33556713-c85b-ab0f-554e-94a40f9d418e@telenet.be \
--to=maximedevos@telenet.be \
--cc=aconchillo@gmail.com \
--cc=guile-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.
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).