From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: patch PR25583: debuginfod bsdtar for deb
Date: Fri, 27 Mar 2020 01:13:05 +0100 [thread overview]
Message-ID: <53baf558b0fd95968d6e8c739307fb7489b9fa83.camel@klomp.org> (raw)
In-Reply-To: <20200325145747.GA8051@redhat.com>
Hi Frank,
On Wed, 2020-03-25 at 10:57 -0400, Frank Ch. Eigler via Elfutils-devel wrote:
> Author: Frank Ch. Eigler <fche@redhat.com>
> Date: Wed Mar 25 10:55:53 2020 -0400
>
> PR25583: debuginfod: prefer bsdtar to dpkg for .deb handling
>
> It turns out a bsdtar subshell can do the job of dpkg-deb.
> bsdtar comes from/with libarchive so it should be available
> everywhere.
The patch itself looks correct. And it is a win for non-deb based
systems since the bsdtar dependencies are already there. But for .deb
based systems it is more likely they already have dpkg installed, while
bsdtar might be a separate install/package. And it still needs to spawn
an external process.
I looked at the buildbot workers and none had bsdtar installed. I have
installed it now on the i386, debian/fedora/centos-x86_64, arm32 and
arm64 workers and have requested it to be installed on the s390x and
ppc64[le] workers.
I am not against this patch, but I do wonder if it should not try to
fall back on dpkg if bsdtar isn't installed.
Cheers,
Mark
next prev parent reply other threads:[~2020-03-27 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 14:57 Frank Ch. Eigler
2020-03-27 0:13 ` Mark Wielaard [this message]
2020-03-27 1:12 ` Frank Ch. Eigler
2020-03-27 1:32 ` Frank Ch. Eigler
2020-03-27 13:18 ` Frank Ch. Eigler
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=53baf558b0fd95968d6e8c739307fb7489b9fa83.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.com \
/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.
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).