From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: guix-devel@gnu.org
Subject: How to find binaries in libexec dir?
Date: Sat, 16 Apr 2022 16:21:50 -0700 [thread overview]
Message-ID: <87mtgky5pt.fsf@contorta> (raw)
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
Diffoscope uses *lots* of optional tools for which it would be
impractical to embed all the tool references in the guix
packaging... instead, for the most part, diffoscope relies on PATH to
find helper utilities to decode various file formats into something more
human readable...
But libxmlb ships the xb-tool binary in libexec, which diffoscope cannot
find on guix. For Debian, diffoscope just basically adds the
corresponding directory to PATH, and it's basically a single directory,
but I'm not sure how I'd do that with guix ...
How do I find all the potential libexec dirs that a user might have in a
given environment? On Guix System, I'll likely have at least the system
profile's libexec, the user's libexec, but as soon as you start using
guix shell, guix shell --container, or source multiple profiles, it's
hard to know where would be "reasonable" to look.
A workaround would be to adjust the libxmlb package so that xb-tool is
also in PATH somehow, but maybe this is bad form?
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2022-04-16 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 23:21 Vagrant Cascadian [this message]
2022-04-17 18:52 ` How to find binaries in libexec dir? Danny Milosavljevic
2022-04-17 19:27 ` Vagrant Cascadian
2022-04-17 19:54 ` Liliana Marie Prikler
2022-04-17 20:42 ` Vagrant Cascadian
2022-04-19 7:17 ` Allan Adair
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=87mtgky5pt.fsf@contorta \
--to=vagrant@reproducible-builds.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).