|
From: Loïc M. <lo...@do...> - 2010-02-12 23:04:48
|
Hey there! I was poking at the valgrind Ubuntu build (valgrind was apparently broken and SVN tip worked fine and had all these nice ARM patches... :-) and noticed that the package is huge due to the 121M of unstripped binaries in /usr/lib/valgrind. debian/changelog says: valgrind (1.0pre2-2) unstable; urgency=low * removed call to dh_strip, at upstream's request * Added an override against unstripped-binary-or-object, after shaleh gave green light. -- Cyrille Chepelov <cy...@ch...> Fri, 21 Jun 2002 15:12:24 +0200 I'd like to readd stripping, but am checking here just in case it's something you really care we don't do. Thanks! -- Loïc Minier |
|
From: Loïc M. <lo...@do...> - 2010-03-28 15:06:56
|
On Sat, Feb 13, 2010, Loïc Minier wrote: > * removed call to dh_strip, at upstream's request > > I'd like to readd stripping, but am checking here just in case it's > something you really care we don't do. Hmm replying to myself, I came across README_PACKAGERS which says: -- Don't strip the debug info off lib/valgrind/$platform/vgpreload*.so in the installation tree. Either Valgrind won't work at all, or it will still work if you do, but will generate less helpful error messages. [...] -- Don't strip symbols from lib/valgrind/* in the installation tree. Doing so will likely cause problems. Removing the line number info is probably OK (at least for some of the files in that directory), although that has not been tested by the Valgrind developers. It sounds as if I might be able to strip some of the debug info for some of the files under lib/valgrind and debug info from bin/* for the rare binaries in there. This seems risky and would probably save a limited amount of space, so I wont do that. -- Loïc Minier |