unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Gordon Quad via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 53915@debbugs.gnu.org, ludo@gnu.org
Subject: bug#53915: No way of replacing an input in modify-input syntax structure but keep all the outputs
Date: Fri, 11 Feb 2022 10:26:14 +0000	[thread overview]
Message-ID: <20220211102614.rxbfjemppztfhlb2@citadel.info> (raw)
In-Reply-To: <0dac06dbcb20fa32baf87df3460ebc102652f31e.camel@gmail.com>

On Thu, Feb 10, 2022 at 09:03:56PM +0100, Liliana Marie Prikler wrote:
> Am Donnerstag, dem 10.02.2022 um 10:09 +0000 schrieb Gordon Quad:
> > poppler package include glib as a native-input with "bin" output.
> > 
> > If I am doing the following:
> > 
> > (package/inherit poppler
> >     (native-inputs
> >         (modify-inputs (package-native-inputs poppler)
> >             (replace "glib" my-glib))))
> > 
> > poppler's build will fail becuase replace syntax will replace "glib"
> > package erasing its outputs. I can specify output explicitly by doing
> > (replace "glib" (my-glib "bin")) in this case, but that makes mass
> > input modification difficult (e.g. if i want to replace all instances
> > of glib to my-glib).
> I think the problem here is that "glib" serves double duty as both
> "glib:out" and "glib:bin".  IMHO we should probably add the output
> argument to the label (with a colon separator, of course) if one is
> given.
> 
> I'm CC'ing Ludo because he implemented the feature and might know more
> than me regarding its design.
Well, just grepping the code for glib I found plenty of places where it
is specified as ("glib" ,glib "bin"), and glib is the only package that
I checked so far. So what you telling me that official policy is to use
labeling convesion as "package:output" but not all the old code converted
to that yet?




  reply	other threads:[~2022-02-11 10:27 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 [this message]
2022-03-08 16:11 ` Ludovic Courtès
2022-03-08 20:28   ` Liliana Marie Prikler
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

  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=20220211102614.rxbfjemppztfhlb2@citadel.info \
    --to=bug-guix@gnu.org \
    --cc=53915@debbugs.gnu.org \
    --cc=gordon@niflheim.info \
    --cc=liliana.prikler@gmail.com \
    --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 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).