public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/27351] please add a debugedit binary to elfutils
Date: Thu, 18 Feb 2021 12:50:54 +0000	[thread overview]
Message-ID: <bug-27351-10460-abBYnNVIIB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27351-10460@http.sourceware.org/bugzilla/>

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

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
We should obviously discuss with the rpm maintainers. But I think it might
actually be easier to have debugedit be its own project, just like e.g. dwz is.
Then it can have its own release schedule and the build setup can be small and
easy. Using autoconf autotests will then also be more natural.

And should it just be debugedit itself or also the find-debuginfo.sh script
that rpm ships. That one is more integrated/tied to rpm at the moment. But
might also be useful independently.

If debugedit (and possibly find-debuginfo.sh) would be released independently
of rpm then making sure things keep being compatible is really important. We'll
probably need to add a buildbot that builds/tests the project together for
that.

But first we need to know what the rpm maintainers think of this idea. It would
probably be a good idea to raise this on the
http://lists.rpm.org/mailman/listinfo/rpm-ecosystem mailinglist.

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

  parent reply	other threads:[~2021-02-18 12:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 11:25 [Bug tools/27351] New: " doko at debian dot org
2021-02-05 13:28 ` [Bug tools/27351] " ldv at sourceware dot org
2021-02-05 16:10 ` christian.morales.vega at gmail dot com
2021-02-18 12:50 ` mark at klomp dot org [this message]
2021-02-19  8:15 ` mliska at suse dot cz
2021-02-19 12:20 ` pmatilai at laiskiainen dot org
2021-02-19 20:25 ` mark at klomp dot org
2021-04-26 16:19 ` mark at klomp dot org

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-27351-10460-abBYnNVIIB@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).