unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: (ice-9 base64)?
Date: Fri, 19 Aug 2022 12:06:01 +0200	[thread overview]
Message-ID: <bf446e06-5da6-ab3e-5f1f-1bdb301cab06@telenet.be> (raw)
In-Reply-To: <CA+XASoU93LKF5jdaDfumV_R9f5Gof3_rwEFuLTKUn6dmsfjfVA@mail.gmail.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 2121 bytes --]

On 19-08-2022 02:20, Aleix Conchillo Flaqué wrote:

> So, what do you think would be the way to proceed in order to include 
> a base64 implementation in Guile itself?
>
> For example:
>
> 1. Add (ice-9 base64) (or (encoding base64)) to Guile and let new 
> projects and existing projects to update with conditional module 
> loading to support old versions of Guile.
> 2. Do unbundling in Guix packages both for projects that have not 
> updated upstream and for projects in (1). The unbundling would be done 
> by pointing to Guix's (or guile-gcrypt) base64 implementation, or is 
> there a way they could point to Guile's implementation?

If the canonical location of base64 becomes Guile itself instead of 
guile-gcrypt, then it needs to be pointed at Guile's base64. Likewise, 
Guix' base64 implementation would need to be replaced by Guile's, with a 
fallback.

I don't see why we would point to Guix' implementation, it's missing 
some bug fixes.

>
> Does that make sense or am I still missing something (I'm about to 
> catch a cold so my brain is not working quite well this week)? 
> Originally, I was thinking only in (1).

Except for the remark about (1), I think so.  I think the following list 
is a bit more clear though:

 1. Add (ice-9 base64) to Guile (or another name (encoding base64)).
 2. Inform a few upstreams that used to include a copy of base64 that it
    is now part of Guile itself -- those upstreams can then remove their
    local copy and use Guile's base64, and do conditional module loading
    if they cannot increase their minimal Guile version yet.
 3. In Guix, we will have to update Guile to a new version that has the
    base64 module and remove the local fallback copies.  And if upstream
    refuses patches to use Guile's base64 (maybe with a fallback), then
    it will need to be patched locally in Guix.

On (2): I don't think it's necessary to contact _all_ the upstreams, 
though to give a good example it would be nice to contact some of them.

(3) is a Guix concern, not really a Guile concern.

Greetings,
Maxime.


[-- Attachment #1.1.1.2: Type: text/html, Size: 3791 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 --]

      reply	other threads:[~2022-08-19 10:06 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
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 [this message]

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=bf446e06-5da6-ab3e-5f1f-1bdb301cab06@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=aconchillo@gmail.com \
    --cc=guile-devel@gnu.org \
    --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.
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).