public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "pmatilai at redhat dot com" <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:21:50 +0000	[thread overview]
Message-ID: <bug-30097-13298-F5xqTcqgsA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30097-13298@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30097

--- Comment #4 from Panu Matilainen <pmatilai at redhat dot com> ---
> cpio is just known to always be there.

Note that rpm itself does not use the external cpio command for anything at
all. The only reason rpm-build in Fedora depends on cpio is because nobody
thought to remove the dependency when the debuginfo-stuff got split.

While we've come to expect to cpio being always there, few packages actually
depend on it.

I'm not arguing for replacing, cpio is tiny enough that it hardly matters at
all. Just FWIW.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-08-28 11:21 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
2023-08-28 11:13 ` kloczko.tomasz at gmail dot com
2023-08-28 11:21 ` pmatilai at redhat dot com [this message]
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-F5xqTcqgsA@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).