From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Lirzin <mthl@gnu.org>
Cc: 30130@debbugs.gnu.org
Subject: bug#30130: Add ‘guix whereis’ command
Date: Wed, 17 Jan 2018 15:05:42 +0100 [thread overview]
Message-ID: <877esg60nd.fsf@gnu.org> (raw)
In-Reply-To: <871sirf3fo.fsf@gnu.org> (Mathieu Lirzin's message of "Mon, 15 Jan 2018 18:16:11 +0100")
Mathieu Lirzin <mthl@gnu.org> skribis:
> I would find really useful if Guix was providing a tool similar to what
> ‘dnf whatprovides’ or ‘apt-file’ does. I mean something to check what
> packages provides a particular file (executable/manual/library).
This has been discussed before, and can be summarized this way:
1. Finding files that are already in your store could be done easily,
using ‘updatedb’ or something similar.
2. Finding files from packages not in your store is trickier: it
involves getting info from a build farm server typically.
If we address #1 in a Guix-specific way (automatically populating a file
database upon build completion), then perhaps we could arrange for ‘guix
publish’ to publish that info.
Ludo’.
next prev parent reply other threads:[~2018-01-17 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 17:16 bug#30130: Add ‘guix whereis’ command Mathieu Lirzin
2018-01-17 14:05 ` Ludovic Courtès [this message]
2018-12-17 9:39 ` swedebugia
2018-12-17 12:03 ` Ricardo Wurmus
2018-12-17 20:55 ` Efraim Flashner
2024-01-30 16:13 ` Ricardo Wurmus
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=877esg60nd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30130@debbugs.gnu.org \
--cc=mthl@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).