I looked a bit into this yesterday, just to see what sort of effort we'd be
talking about to have rpm understand the buildid from go (as opposed to gnu):
- The go-buildid appears to be ASCII SHA1(based on its length), this would
require modifications to debugedit and librpmbuild side as both assume the
digest is stored in binary format
- There's partial support for the Go buildid in elfutils, added via
https://bugzilla.redhat.com/show_bug.cgi?id=1295951 (which is what you see with
eu-readelf) but as noted in the bug, more is needed. For example
dwelf_elf_gnu_build_id() only knows about GNU buildid as the name implies and
there's no Go buildid counterpart.
For now I think we just need to state that only GNU toolchain buildids are
supported, for others there's the simple workaround of disabling buildid
requirement in the package that you're already using.
If/when elfutils adds full support for other variants we can reconsider it in
rpm, but I'll leave that up to Mark who's the maintainer of both elfutils and
debugedit/buildid stuff in rpm.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/367#issuecomment-372947462
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
