From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug find-debuginfo/30097] Q: why find-debuginfo script uses cpio?
Date: Mon, 28 Aug 2023 11:04:22 +0000 [thread overview]
Message-ID: <bug-30097-13298-h2uAyguR2i@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30097-13298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30097
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
(In reply to kloczek from comment #0)
> Trying to minimize base build build env I found that only package which
> needs cpio is find-debuginfo scipt.
> I have difficulty ith understandig why it needed to try to remove that
> dependency.
>
> Is it reall necessary to use cpio in this case?
It is just an convenient way to package up a bunch of files.
It could be replaced with any other packaging system.
cpio is just known to always be there.
What would you suggest instead? And do you have a working patch?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-28 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 3:04 [Bug find-debuginfo/30097] New: " kloczko.tomasz at gmail dot com
2023-02-08 6:25 ` [Bug find-debuginfo/30097] " pmatilai at redhat dot com
2023-08-28 11:04 ` mark at klomp dot org [this message]
2023-08-28 11:13 ` kloczko.tomasz at gmail dot com
2023-08-28 11:21 ` pmatilai at redhat dot com
2023-08-28 11:28 ` mark at klomp dot org
2023-08-28 11:32 ` kloczko.tomasz at gmail 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-30097-13298-h2uAyguR2i@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=debugedit@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).