From: "Ludovic Courtès" <ludo@gnu.org>
To: divoplade <d@divoplade.fr>
Cc: 44130@debbugs.gnu.org
Subject: [bug#44130] [PATCH] Add a recursive version of mkdir-p
Date: Fri, 23 Oct 2020 15:12:44 +0200 [thread overview]
Message-ID: <87y2jxnl0z.fsf@gnu.org> (raw)
In-Reply-To: <6ff632f5c1e378647cecc7177b7018fb8a0ee6d4.camel@divoplade.fr> (divoplade's message of "Thu, 22 Oct 2020 01:29:48 +0200")
Hi!
divoplade <d@divoplade.fr> skribis:
> I need this mkdir-p function in any non-trivial program I write. I had
> 3 bad choices:
>
> 1. Lobby guile to provide this function out of the box (this will take
> time);
> 2. Copy that of guix, or gash, or any other: this does not seem
> acceptable to me, because this function will surely evolve (for
> instance, if guile gets suport for mingw and we start running guile
> programs on windows) and I don't want to update more than one version
> of this function;
> 3. Depend on guix, gash or another package: this would be too large a
> dependency for my programs.
>
> So I wrote it in its own package and I intend to depend on it for my
> other projects. It would be best if you could accept this package in
> guix proper.
>
> What do you think?
I have nothing against adding this package to Guix, but…
Do you realize that the package definition is longer than the ‘mkdir-p’
procedure itself? :-)
I think npm packages are too fine-grain; I don’t think this is the
approach to follow for Guile.
It’s likely that packages that need ‘mkdir-p’ also need other high-level
file system operations that Gash (say) provides. In that case, I’d
encourage people to depend on Gash. If Gash is too big a dependency for
the project, including its own copy of this 24-line procedure is
probably acceptable.
All that said, I do think that Guile itself should eventually include
some of the utilities found in (guix build utils) or Gash. For
instance, it recently got a new ‘pipeline’ procedure, which comes from
Gash, and I think it’s a great addition. This is the way to go in the
longer term.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2020-10-23 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 23:29 [bug#44130] [PATCH] Add a recursive version of mkdir-p divoplade
2020-10-23 13:12 ` Ludovic Courtès [this message]
2020-10-23 14:14 ` divoplade
2020-10-23 16:37 ` Ludovic Courtès
2020-10-23 17:12 ` divoplade
2020-10-26 16:57 ` bug#44130: " Ludovic Courtès
2020-10-23 19:36 ` [bug#44130] " zimoun
2020-10-23 22:00 ` [bug#44130] Recursive mkdir divoplade
2020-10-23 22:11 ` [bug#44130] [PATCH] Add a recursive version of mkdir-p divoplade
2020-10-23 20:01 ` Leo Prikler
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=87y2jxnl0z.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44130@debbugs.gnu.org \
--cc=d@divoplade.fr \
/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).