From: Chris Marusich <cmmarusich@gmail.com>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Given a file, find the package that builds it
Date: Fri, 30 Mar 2018 06:53:58 +0200 [thread overview]
Message-ID: <87h8oy4109.fsf_-_@gmail.com> (raw)
In-Reply-To: <87woxv4inn.fsf@gmail.com> (Pierre Neidhardt's message of "Thu, 29 Mar 2018 09:50:28 +0530")
[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]
Pierre Neidhardt <ambrevar@gmail.com> writes:
>>> A more general question: How do I find to which non-installed package a
>>> filename belongs?
>>
>> Guix does not currently know anything about the files inside each
>> package, I typically do a web search...
>
> This is too bad, I believe it's an important feature for any package
> manager.
> As far as I can tell, `portage` and `pacman` can both do it.
>
> Any plan regarding guix?
I don't know of any plan at the moment. Nothing is stopping a motivated
individual from creating a mapping of packages to programs, of course,
and then making it available to anyone who is interested.
Here's one idea: what if somebody defined a package which used every
other package as input, scanned their output paths and created such a
mapping, and then wrote that mapping (or built a tool to easily query
that mapping) as its own output? You could call it the "xiug" package!
;-)
Until a solution is created, I find that the following heuristic usually
works (where $program is the name of the program I'm interested in):
* Try: guix package --search=$program
* Search the Internet for $program, and find out what package provides
the $program on existing distributions. Then try "guix package
--search=$package" where $package is the package name used in the
other distro. The name is often the same or similar.
* Brute force search your local store for the build output:
find -L /gnu/store -iname "*${program}*"
* Ask on IRC or email!
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-03-30 4:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 7:09 Locale error: Falling back to C locale Pierre Neidhardt
2018-03-27 9:53 ` Ludovic Courtès
2018-03-27 10:19 ` Pierre Neidhardt
2018-03-27 21:00 ` Ludovic Courtès
2018-03-28 4:44 ` Pierre Neidhardt
2018-03-28 20:21 ` Marius Bakke
2018-03-29 4:20 ` Pierre Neidhardt
2018-03-29 16:53 ` Marius Bakke
2018-03-29 17:04 ` Pierre Neidhardt
2018-03-29 17:12 ` Marius Bakke
2018-03-29 17:45 ` Pierre Neidhardt
2018-03-29 20:15 ` Ricardo Wurmus
2018-03-30 4:13 ` Pierre Neidhardt
2018-03-30 9:48 ` Ricardo Wurmus
2018-03-30 10:14 ` Pierre Neidhardt
2018-03-30 4:53 ` Chris Marusich [this message]
2018-03-30 6:16 ` Given a file, find the package that builds it Oleg Pykhalov
2018-03-30 6:22 ` Pierre Neidhardt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8oy4109.fsf_-_@gmail.com \
--to=cmmarusich@gmail.com \
--cc=ambrevar@gmail.com \
--cc=help-guix@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.