|Subject:||Re: (ice-9 base64)?|
|Date:||Fri, 19 Aug 2022 12:06:01 +0200|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0|
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?
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:
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.
Description: OpenPGP public key
Description: OpenPGP digital signature
|[Prev in Thread]||Current Thread||[Next in Thread]|