all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: divoplade <d@divoplade.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 44130@debbugs.gnu.org
Subject: [bug#44130] [PATCH] Add a recursive version of mkdir-p
Date: Fri, 23 Oct 2020 19:12:17 +0200	[thread overview]
Message-ID: <3dca955c97222648074515b1a2c5ace96a2f1fd6.camel@divoplade.fr> (raw)
In-Reply-To: <871rholwzj.fsf@gnu.org>

Le vendredi 23 octobre 2020 à 18:37 +0200, Ludovic Courtès a écrit :
> 
> What I was questioning is the temptation to make one-function
> packages
> as is common for instance in npm.

Ah, so I can summarize. My solutions are:

1. Guile provides mkdir-p: Perfect!
2. I put the function in a package: not great, but acceptable.
3. I depend on gash: not acceptable, there's only mkdir-p that's
interesting, the rest is for advanced system tools.
4. I copy that function around: not acceptable.

So, there's no temptation to make one-function packages.

Should I understand that you question the integration of one-function
packages into guix? If you don't want it in guix, then it's fine, I can
just use it only for myself, I have my own channel. In which case,
please just say so, so we can all move on to more interesting things.

Best regards,

divoplade





  reply	other threads:[~2020-10-23 17: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
2020-10-23 14:14   ` divoplade
2020-10-23 16:37     ` Ludovic Courtès
2020-10-23 17:12       ` divoplade [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3dca955c97222648074515b1a2c5ace96a2f1fd6.camel@divoplade.fr \
    --to=d@divoplade.fr \
    --cc=44130@debbugs.gnu.org \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.