From: Maxime Devos <maximedevos@telenet.be>
To: Attila Lendvai <attila@lendvai.name>, guix-devel <guix-devel@gnu.org>
Subject: Re: using an SRFI that is not available in Guile
Date: Wed, 12 Jan 2022 17:09:49 +0000 [thread overview]
Message-ID: <94d412c429288b265a22aedd8eff3b3aa35b32e8.camel@telenet.be> (raw)
In-Reply-To: <6vmHCdZdAWsjqvLgmVNEZclQ-JbdRJLfGzLNphX3EbevcslD-_TkMuHA1MwIylOfbe3DkDXYCbx5WT_Q44sC1Qed5MsBUg2xxZKhUbChGGs=@lendvai.name>
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
Attila Lendvai schreef op wo 12-01-2022 om 16:46 [+0000]:
> dear Guixers,
>
> when working on the (gnu services configuration) module, i would like
> to use srfi-189, which is not available in Guile
> (https://srfi.schemers.org/srfi-189/srfi-189.html).
>
> is there any way to add it, or an already established custom for such
> a situation? e.g. adding the .scm file to Guix, preferrably late in
> the load order, until Guile catches up and shadows it with its own?
Instead of bundling it in Guix (which would prevent Guix from being
packaged in Guix, due to point 8 in (guix)Submitting Patches), how
about making it a package available for anyone (not only Guix)?
Have a look at the Guix packages guile-srfi-89/145/158/159/180.
Basically, SRFIs can be implemented like any other module in Guile
and don't have a special status in Guile (except for cond-expand and
some special syntax for importing SRFI modules -- maybe in 'library',
not sure where exactly).
FWIW I don't think there is any need for Guile to ship an
implementation for all SRFIs by itself when they can be implemented as
separate libraries that can be installed with
$FAVOURITE_PACKAGE_MANAGER.
If at some point an implementation of the SRFI is moved into Guile,
then the package definition of guile-srfi-NNN can be removed from Guix
and guile-srfi-NNN can be removed from package inputs.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-12 17:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 16:46 using an SRFI that is not available in Guile Attila Lendvai
2022-01-12 17:01 ` Attila Lendvai
2022-01-12 17:09 ` Maxime Devos [this message]
2022-01-13 9:55 ` Attila Lendvai
2022-01-13 10:49 ` Maxime Devos
2022-01-13 18:20 ` Attila Lendvai
2022-01-13 20:48 ` Attila Lendvai
2022-01-14 12:02 ` Maxime Devos
2022-01-17 13:45 ` Attila Lendvai
2022-01-13 10:53 ` Maxime Devos
2022-01-13 10:56 ` Maxime Devos
2022-01-18 15:09 ` Ludovic Courtès
2022-01-18 17:06 ` Attila Lendvai
2022-01-19 10:34 ` Ludovic Courtès
2022-01-21 13:59 ` Attila Lendvai
2022-01-24 15:41 ` Ludovic Courtès
2022-01-24 23:02 ` Attila Lendvai
2022-02-05 11:13 ` 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=94d412c429288b265a22aedd8eff3b3aa35b32e8.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=attila@lendvai.name \
--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.
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).