GNOME Bugzilla – Bug 695816
Split debuginfo
Last modified: 2013-04-02 19:07:59 UTC
The current -runtime tree is about 2G. Completely stripped, 1.1G. The biggest contributors are anything C++, like webkitgtk, followed closely by spidermonkey. So yes, we need to do split debuginfo. Prior art: debhelper: http://anonscm.debian.org/gitweb/?p=debhelper/debhelper.git;a=blob;f=dh_strip;h=ea5315a3b12999cd1b63d956f62ffa1b9ca6a9ca;hb=HEAD Looks not too bad (for Perl). rpm: http://rpm.org/gitweb?p=rpm.git;a=blob;f=tools/debugedit.c;h=f48d6f7a103188c769e5b1c06b165d82047c840f;hb=HEAD Eww...it's not clear to me why this is such an overly complex program. Perhaps it predates elfutils? Gentoo/portage: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=blob;f=bin/ebuild-helpers/prepstrip;h=fb20777e886af12ccb2942254c2599e4ec6b6d1f;hb=HEAD Oh but wait, interestingly, it appears default to using a fork of debugedit: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-util/debugedit/debugedit-5.3.5-r1.ebuild?view=markup There's also this bug I found: http://code.google.com/p/chromium-os/issues/detail?id=21524 But maybe that predates use of debugedit?
Ah, I think I understand; debugedit is about the "source installation" feature, on top of the raw debuginfo lookup. The binaries have embedded source paths in them, which it edits. I think we can probably punt on that and just do what Debian does.
https://git.gnome.org/browse/gnome-ostree/commit/?id=baaeef3242d74dcf46245f2516662dcdfc9ea678