From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/25583] Use libarchive to extract packages?
Date: Sat, 22 Feb 2020 00:57:00 -0000 [thread overview]
Message-ID: <bug-25583-10460-4Fbkgs6ule@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25583-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25583
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2020-02-22
CC| |fche at redhat dot com
Ever confirmed|0 |1
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
Interesting idea. OTOH, rpm2cpio and dpkg binaries are not too hard to come
by.
One can experiment with the former already with git-master debuginfod with the
"-Z .rpm" option instead of "-R". Performance seems to be roughly the same.
The latter is less compelling in that it'd require hard-coding the inner
data.tar.xz name and its processing ... meh.
Maybe the status quo is good enough?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-02-22 0:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 11:08 [Bug debuginfod/25583] New: " ross at burtonini dot com
2020-02-22 0:57 ` fche at redhat dot com [this message]
2020-02-25 12:12 ` [Bug debuginfod/25583] " mark at klomp dot org
2020-02-25 15:21 ` fche at redhat dot com
2020-02-25 19:31 ` fche at redhat dot com
2020-03-03 8:51 ` [Bug debuginfod/25583] Use libarchive to extract .deb packages? mark at klomp dot org
2020-03-03 11:25 ` fche at redhat dot com
2020-03-23 15:19 ` fche at redhat dot com
2020-03-25 14:58 ` fche at redhat dot com
2020-03-26 19:52 ` fche at redhat dot com
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=bug-25583-10460-4Fbkgs6ule@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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.
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).