From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: (hidden) wrapper+dependencies inconsistency=manifest fails?
Date: Tue, 24 Sep 2019 10:01:14 +0200 [thread overview]
Message-ID: <875zlinmwl.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ1uQ+t09ykBhvJ-6=eDXCZoe7Ds+vNzPQAo_hOGBhoZHQ@mail.gmail.com> (zimoun's message of "Fri, 20 Sep 2019 18:18:01 +0200")
Hi!
zimoun <zimon.toutoune@gmail.com> skribis:
> This command lists the dependencies of the "guix" package.
>
> guix package --show=guix | recsel -p dependencies
>
> Then this command fails:
> guix package --show=autoconf-wrapper
>
> It is expected because the "wrapper" is not a "real" package and it is
> not exposed. Only the package "autoconf" is.
>
>
> Therefore, you cannot chain:
>
> guix package -i `guix package --show=guix | recsel -P dependencies`
>
> guix package: error: autoconf-wrapper: package not found for version 2.69
Yes, but it’s a fact of life IMO. :-)
> Moreover, the name in "native-inputs" is not consistent with the
> declared name. I mean:
> guix repl
>> ,use(guix)
>> ,use(gnu packages package-management)
>> (package-native-inputs guix)
>> (map car (package-native-inputs guix))
This gives you the list of labels for each input. The labels do _not_
have to match package names; they can be anything, there can even be
duplicates, etc. You should not rely on them at all to identify
packages.
Eventually, once build systems use gexp, I hope we can even get rid of
these labels. Guix 2.0.
Does that make sense?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-09-24 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 16:18 (hidden) wrapper+dependencies inconsistency=manifest fails? zimoun
2019-09-24 8:01 ` Ludovic Courtès [this message]
2019-09-24 16:52 ` zimoun
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=875zlinmwl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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 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).