From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Mark Wielaard <mark@klomp.org>
Cc: rpm-ecosystem@lists.rpm.org, debugedit@sourceware.org
Subject: Re: [Rpm-ecosystem] debugedit project setup
Date: Mon, 29 Mar 2021 14:00:55 +0300 [thread overview]
Message-ID: <20210329110055.GC11628@altlinux.org> (raw)
In-Reply-To: <20210325211338.GI2685@wildebeest.org>
Hi Mark,
On Thu, Mar 25, 2021 at 10:13:38PM +0100, Mark Wielaard wrote:
> Hi Panu,
>
> I added debugedit@sourceware.org to the CC.
>
> On Tue, Mar 23, 2021 at 03:52:53PM +0200, Panu Matilainen wrote:
> > On 3/23/21 2:29 PM, Panu Matilainen wrote:
> > > On 3/22/21 7:42 PM, Mark Wielaard wrote:
> > > > There is a test debugedit-0.1 release to see whether this works. But I
> > > > would like to make sure first that things are setup so that flatpak and
> > > > rpm can use this as is before people start packaging it. Once we know
> > > > it can be used as replacement for the built-in rpm/flatpak debugedit we
> > > > do a proper debugedit 1.0 release.
> > >
> > > Awesome. I'll make it a priority to see that we transition, if at all
> > > possible, to the external debugedit in rpm 4.17 already. Stay tuned...
> >
> > FWIW, here's a quick-n-dirty package of debugedit 0.1:
> >
> > https://laiskiainen.org/rpm/debugedit/
>
> Nice, thanks. Would it make sense to add the debugedit.spec to the
> debugedit sources themselves so people can easily create an rpm?
>
> Does it actually make sense to install everything under bindir?
At least debugedit executable has a documented command line interface,
so I'd say it belongs to bindir.
--
ldv
next prev parent reply other threads:[~2021-03-29 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 17:42 Mark Wielaard
2021-03-23 12:29 ` [Rpm-ecosystem] " Panu Matilainen
[not found] ` <5c1d49ba-5a01-e6b2-dbc7-3cd64d552688@redhat.com>
2021-03-25 21:13 ` Mark Wielaard
2021-03-26 1:11 ` Mark Wielaard
2021-03-29 8:21 ` Panu Matilainen
2021-03-29 8:31 ` Panu Matilainen
2021-03-29 11:00 ` Dmitry V. Levin [this message]
2021-06-18 8:37 ` Panu Matilainen
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=20210329110055.GC11628@altlinux.org \
--to=ldv@altlinux.org \
--cc=debugedit@sourceware.org \
--cc=mark@klomp.org \
--cc=rpm-ecosystem@lists.rpm.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).