From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Gordon Quad" <gordon@niflheim.info>
Cc: 53915@debbugs.gnu.org
Subject: bug#53915: No way of replacing an input in modify-input syntax structure but keep all the outputs
Date: Tue, 08 Mar 2022 21:28:43 +0100 [thread overview]
Message-ID: <33debb0b55b52a09d268c07ec8f2355f928de62a.camel@gmail.com> (raw)
In-Reply-To: <87zgm04e6f.fsf@gnu.org>
Am Dienstag, dem 08.03.2022 um 17:11 +0100 schrieb Ludovic Courtès:
> [...]
> With the patch below, we get more sensible behavior:
>
> --8<---------------cut here---------------start------------->8---
> scheme@(guile-user)> (modify-inputs (append $5 $4)
> (replace "glib" xpdf))
> $8 = (("glib" #<package xpdf@4.03 gnu/packages/pdf.scm:395
> 7f9b1457c9a0>) ("pkg-config" #<package
> pkg-config@0.29.2 gnu/packages/pkg-config.scm:36 7f9b13a30580>)
> ("glib" #<package xpdf@4.03 gnu/packages/pdf.scm:395 7f9b1457c9a0>
> "bin") ("gobject-introspection" #<package
> gobject-introspection@1.66.1 gnu/packages/glib.scm:428
> 7f9b12994e70>))
> --8<---------------cut here---------------end--------------->8---
>
> If that makes sense to you, I’ll go ahead with this change and adjust
> documentation accordingly.
Sounds better than my own suggestion, since it'll keep working the way
it did even when labels are eventually dropped. If more control is
needed, we can always later extend it to support (replace ("label"
"output") (package output)). WDYT?
Cheers
next prev parent reply other threads:[~2022-03-08 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 10:09 bug#53915: No way of replacing an input in modify-input syntax structure but keep all the outputs Gordon Quad via Bug reports for GNU Guix
2022-02-10 20:03 ` Liliana Marie Prikler
2022-02-11 10:26 ` Gordon Quad via Bug reports for GNU Guix
2022-03-08 16:11 ` Ludovic Courtès
2022-03-08 20:28 ` Liliana Marie Prikler [this message]
2022-03-16 14:53 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33debb0b55b52a09d268c07ec8f2355f928de62a.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=53915@debbugs.gnu.org \
--cc=gordon@niflheim.info \
--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.