unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: How to find binaries in libexec dir?
Date: Sun, 17 Apr 2022 12:27:24 -0700	[thread overview]
Message-ID: <87r15v7boj.fsf@contorta> (raw)
In-Reply-To: <20220417205242.5f3cb12c@scratchpost.org>

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

On 2022-04-17, Danny Milosavljevic wrote:
> On Sat, 16 Apr 2022 16:21:50 -0700
> Vagrant Cascadian <vagrant@reproducible-builds.org> wrote:
>
>> But libxmlb ships the xb-tool binary in libexec, which diffoscope cannot
>> find on guix.
...
> I've looked upstream https://github.com/hughsie/libxmlb and it says, very close
> to the beginning (so it's a main feature apparently):
>
>>$ xb-tool compile fedora.xmlb fedora.xml.gz
>
> Well, for that to work, xb-tool should be in bin.
>
> I'd file a bug report with libxmlb to move xb-tool to bin.

Good suggestion, we'll see where it goes!

  Please install xb-tool into bin instead of libexec
  https://github.com/hughsie/libxmlb/issues/123


In the meantime, would it be reasonable to workaround this in guix by
patching libxmlb to include xb-tool in bin, either by moving it there,
or symlinking it from there?


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2022-04-17 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16 23:21 How to find binaries in libexec dir? Vagrant Cascadian
2022-04-17 18:52 ` Danny Milosavljevic
2022-04-17 19:27   ` Vagrant Cascadian [this message]
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=87r15v7boj.fsf@contorta \
    --to=vagrant@reproducible-builds.org \
    --cc=dannym@scratchpost.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).