From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>, bug-guix@gnu.org
Subject: Re: guix environment
Date: Tue, 20 Jan 2015 22:43:44 +0100 [thread overview]
Message-ID: <87egqpyvov.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPMYaX+=UFHGbFOFAxLJqx8VaBSRXNKK25SF-Nfk-LAc-g@mail.gmail.com> (Federico Beffa's message of "Tue, 20 Jan 2015 18:21:03 +0100")
Federico Beffa <beffa@ieee.org> skribis:
> I believe that "guix environment" does not consider all outputs
> properly. As one example, when I execute:
>
> guix environment libpeas
>
> the $PATH doesn't include /gnu/store/...glib-2.42.1-bin/bin where
> ("glib:bin" ,glib "bin") is one of the native-inputs of the package.
>
> Is this intentional?
I don’t think so.
On closer inspection, I see two issues:
(define (packages->transitive-inputs packages)
"Return a list of the transitive inputs for all PACKAGES."
(define (transitive-inputs package)
(filter-map (match-lambda
((_ (? package? package)) package)
(_ #f)) ; <---- !
(bag-transitive-inputs
(package->bag package))))
(delete-duplicates
(append-map transitive-inputs packages)))
Here only inputs of the form ("foo" PKG) are considered; things like
("glib" ,glib "bin") are discarded.
(define (for-each-search-path proc inputs derivations pure?)
(let ((paths (map derivation->output-path derivations))) ; <-- !
[...]
Above, ‘derivation->output-path’ considers only the “out” output,
ignoring others if they are needed.
I think these would need to be adjusted. Any takers? :-)
Ludo’.
next parent reply other threads:[~2015-01-20 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKrPhPMYaX+=UFHGbFOFAxLJqx8VaBSRXNKK25SF-Nfk-LAc-g@mail.gmail.com>
2015-01-20 21:43 ` Ludovic Courtès [this message]
2015-01-20 21:56 ` guix environment David Thompson
2015-01-29 23:00 ` David Thompson
2015-02-03 20:29 ` Ludovic Courtès
2015-02-03 21:15 ` David Thompson
2015-02-08 18:22 ` bug#19641: " 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=87egqpyvov.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beffa@ieee.org \
--cc=bug-guix@gnu.org \
--cc=guix-devel@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).