From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 44253-done@debbugs.gnu.org
Subject: [bug#44253] [PATCH] gnu: Add guile-filesystem.
Date: Fri, 30 Oct 2020 00:16:40 +0100 [thread overview]
Message-ID: <87h7qczkpz.fsf@gnu.org> (raw)
In-Reply-To: <e581ddd7a2a361d2c3ab36f43117d8d7725baf34.camel@student.tugraz.at> (Leo Prikler's message of "Wed, 28 Oct 2020 16:43:25 +0100")
Hi Leo!
Leo Prikler <leo.prikler@student.tugraz.at> skribis:
> Am Mittwoch, den 28.10.2020, 16:21 +0100 schrieb Ludovic Courtès:
>> Hi,
>>
>> Leo Prikler <leo.prikler@student.tugraz.at> skribis:
>>
>> > * gnu/packages/guile-xyz.scm (guile-filesystem): New variable.
>> > (guile2.0-filesystem guile2.2-filesystem): New variable.
>>
>> Applied, thanks!
>>
>> However, note that I would not recommend adding 2.0/2.2 variants
>> unless
>> we have a clear use case for it in Guix.
> In this case I simply wanted to make sure, that people could include it
> in projects, whose other dependencies are still stuck on Guile 2.0 or
> Guile 2.2 in Guix. Not really a "clear use case", but that's my
> reasoning.
I guess that’s very valid use case for you as the upstream developer of
‘guile-filesystem’, but not so much for a downstream user of Guix.
> On the topic of those variants, however, would it perhaps be wiser to
> make this a package-mapping instead, or is there a case where `--with-
> input=guile=guile@$EFFECTIVE_VERSION` would be ill-advised?
Unfortunately, ‘--with-input=guile=…’ triggers a world rebuild because
Guile appears deep down in the graph. Otherwise it would be a good use
case. :-)
>> With my Guile hat on, I’d also recommend against using the (ice-9 …)
>> name space, which is in Guile’s backyard. :-)
>>
>> Ludo’.
> I thought poking into Guile's backyard was a best practice in order to
> get the attention of Guile maintainers, as with guile-readline and
> guile-colorized ;)
Heheh, true! But note that guile-readline is actually part of Guile.
> My plan is also to contribute it to Guile proper at some point and then
> perhaps keep that repository as a backport for a while until all
> relevant versions of Guile have a "proper" filesystem module.
Make sense. (I’d recommed “file system” as two words, then. :-))
Cheers,
Ludo’.
prev parent reply other threads:[~2020-10-29 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 12:55 [bug#44253] [PATCH] gnu: Add guile-filesystem Leo Prikler
2020-10-28 15:21 ` bug#44253: " Ludovic Courtès
2020-10-28 15:43 ` [bug#44253] " Leo Prikler
2020-10-29 23:16 ` Ludovic Courtès [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7qczkpz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44253-done@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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).