Re: [Rpm-ecosystem] debugedit project setup

[Panu Matilainen <pmatilai@redhat.com>]

On 3/23/21 2:29 PM, Panu Matilainen wrote:
> On 3/22/21 7:42 PM, Mark Wielaard wrote:
>> Hi,
>>
>> As discussed I setup a separate debugedit project:
>> https://sourceware.org/debugedit/
>>
>> It contains the debugedit and sepdebugcrcfix programs and the find-
>> debuginfo.sh script and the debugedit.at testsuite. I used git-filter-
>> repo to keep the git history of the files from the rpm repo. Then I
>> resynced the libiberty and binutils files and added a minimal
>> automake/autoconf/autotest build system. Replace popt with getopt
>> argument parsing. And use libiberty md5 or sha1 instead of rpmDigest
>> algorithms for build-id updates.
>>
>> 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...

Here goes:

	https://github.com/rpm-software-management/rpm/pull/1712

	- Panu -