From: "nolange79 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/29574] New: debuginfod: allow recursive scanning of archives
Date: Thu, 15 Sep 2022 09:17:28 +0000 [thread overview]
Message-ID: <bug-29574-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29574
Bug ID: 29574
Summary: debuginfod: allow recursive scanning of archives
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: nolange79 at gmail dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Hello,
we organize our build in .tar.xz archives, and pack several of them (and some
meta-info) into zip archives for releases.
The idea would be to just direct debuginfod to the folder of those archives,
ex.:
debuginfod -G -F -Z .xz -Z .zip PATH_TO_ARCHIVES
Unfortunally debuginfod does not recurse here. Perhaps add an Options to either
add max recursion depth, or maybe add '-z .zip' to denote that this is not the
last layer.
This functionality probably already exists, given that .dep has already tars
stuck in ar.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2022-09-15 9:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-29574-10460@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).