From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Guix Devel <guix-devel@gnu.org>
Subject: Finding the store path of a package
Date: Wed, 17 Mar 2021 18:55:54 +0100 [thread overview]
Message-ID: <m17dm5oead.fsf@ordinateur-de-catherine--konrad.home> (raw)
Dear Guix experts,
I wonder if there is a straightforward way to find the store path
corresponding to a package, assuming that the package actually is in the
store. I don't care if it's done via the CLI or via Guile code.
Use case: Looking at the files inside a package. What I do now is "ls
/gnu/store/*<package-name>*", but that usually lists many variants of
the package, and I don't know which of them actually is the current one.
I came up with some Guile code that does the job:
(define (store-path specification)
(let*-values (((package output)
(specification->package+output specification))
((entry)
(package->manifest-entry package output))
((l-entry)
(with-store store
(run-with-store store
(lower-manifest-entry entry (%current-system))))))
(manifest-entry-item l-entry)))
but it also downloads/builds the package if it's not yet in the store,
which is not what I want. In fact, I don't care what happens then the
package is not in the store. Returning a non-existing path is fine,
as is raising an error or returning #f.
Another attempt is "guix package –-list-installed", but this works only
for packages installed in a profile. I am shifting more and more to
on-the-fly environments, meaning that many packages in my store belong
to no profile.
Cheers,
Konrad.
next reply other threads:[~2021-03-17 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 17:55 Konrad Hinsen [this message]
2021-03-17 18:27 ` Finding the store path of a package zimoun
2021-03-18 8:43 ` Konrad Hinsen
2021-03-18 10:45 ` Konrad Hinsen
2021-03-18 12:04 ` zimoun
2021-03-20 13:46 ` Ludovic Courtès
2021-03-22 7:39 ` Konrad Hinsen
2021-03-22 10:03 ` zimoun
2021-03-22 13:12 ` Konrad Hinsen
2021-03-22 16:22 ` Ludovic Courtès
2021-03-22 17:58 ` Konrad Hinsen
2021-04-19 7:08 ` Konrad Hinsen
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=m17dm5oead.fsf@ordinateur-de-catherine--konrad.home \
--to=konrad.hinsen@fastmail.net \
--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).