all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 62008@debbugs.gnu.org
Subject: [bug#62008] [PATCH 0/2] Update Disarchive to 0.5.0
Date: Fri, 10 Mar 2023 17:44:25 +0100	[thread overview]
Message-ID: <87bkl0imja.fsf@gnu.org> (raw)
In-Reply-To: <87bkl0omtg.fsf@gmail.com> (Simon Tournier's message of "Fri, 10 Mar 2023 12:41:47 +0100")

Simon Tournier <zimon.toutoune@gmail.com> skribis:

> On ven., 10 mars 2023 at 09:17, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Hmm good point.  So maybe we need to wrap after all, and also keep
>> propagated inputs (as an example, (guix build download) uses the
>> Disarchive modules directly, not the command.)
>
> I am proposing to have ’package/inherit’,
>
>  1. ’disarchive’: the standalone CLI with wrap
>  2. ’guile-disarchive’: the library with propagated-inputs

I think having a single package is more convenient: it would both
propagate inputs and wrap the binaries as you proposed.

Ludo’.




  reply	other threads:[~2023-03-10 16:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 19:18 [bug#62008] [PATCH 0/2] Update Disarchive to 0.5.0 Simon Tournier
2023-03-06 19:19 ` [bug#62008] [PATCH 1/2] gnu: disarchive: Wrap program instead of using propagated inputs Simon Tournier
2023-03-06 19:19   ` [bug#62008] [PATCH 2/2] gnu: disarchive: Update to 0.5.0 Simon Tournier
2023-03-07  9:51     ` [bug#62008] [PATCH 0/2] Update Disarchive " Ludovic Courtès
2023-03-07  9:49   ` Ludovic Courtès
2023-03-07 10:43     ` Simon Tournier
2023-03-10  8:17       ` Ludovic Courtès
2023-03-10 11:41         ` Simon Tournier
2023-03-10 16:44           ` Ludovic Courtès [this message]
2023-08-16 17:28             ` Simon Tournier
2023-08-18 13:56               ` Ludovic Courtès
2023-08-18 15:03                 ` Simon Tournier
2023-08-19  8:57                 ` Simon Tournier

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=87bkl0imja.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=62008@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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.