The .mdb files are just debuginfo, so there is no good reason why they should blow up the mono package to almost twice its size on the live cd. Please move them to a separate -debuginfo package.
I couldn't figure out how to add the .mdb files to -debuginfo without loosing the regular debuginfo, therefore I stuffed them in a separate mono-mdb subpackage.
Created attachment 293825 [details] patch
Doing this just in the mono package only gets the first level offenders. This should probably be done on a more general level in rpm. Tagging the files and including them in -debuginfo is easy enough, but it's not really feasible to do the excludes automatically. So a little bit of pondering later and I've got a trivial patch to mono-debugger that makes it look in /usr/lib/debug and falling back to looking where it does now. Patches to both find-debuginfo.sh and mono-debugger attached
Created attachment 296700 [details] Support looking in /usr/lib/debug for .mdb files
Created attachment 296701 [details] Move .mdb files to live under /usr/lib/debug
And sticking on the blocker list, as we should really do something about this. Beyond the "it's the right thing to do" argument, it'll also help us quite a bit with space on the livecd (it looks like it saves 29 megs on the installed system and that compresses down to about 10)
Nice
Xavier, can you get to this soon, or else Jeremy I think we should just commit it and be done with it for Fedora 9.
Any update on this ? Would be really good to get this done by Tuesday
We pulled the mono bits off of the livecd and I don't know that this actually gets us enough space back. Moving to F10
Patch added on mono-debugger-0.60. some works need to be done before available in repo, failing on missing file from devel branch.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
What is the status of this ?
I know mono-debugger 2.0 RC 1 has the patch in there. The problem really comes down (AFAICS) to the packaging of mono and debuginfo (as seen in #2 and possibly fixed in #3). Mono's debug symbols are not recognised as the normal debug symbols so they're not picked up on when the debug package is created. As suggested though, if *all* mono packages (and subpackages) are built with debug enabled and then %{name}=debuginfo created by the packager, then this should move things along a bit.
It's worth noting that monodebugger-2.0 is not yet in rawhide.
adding FutureFeature so this bug does not get moved to version "10" at GA
Not really a blocker, since the live cd fits anyway.
Mono-debugger 2.4-pre is in Rawhide and 2.2 is in F10. F9 appears to still have 0.60. Which means we are good, I think. Paul?
The remaining patch is to update find-debuginfo.sh to recognize the *.mdb files as debuginfo and pull them into their own space. Panu, Jeremy, any reason we shouldn't target this against rpm-build, apply it, and be done?
No problems from this end.
Jeremy tells me on IRC that he vaguely recalls some corner cases that may not work. Paul, could you apply the find-debuginfo patches to your local rpm and do some rebuilds of mono packages to see if you can find out what problems arise?
And I'll try to dig into the recesses of my memory (by which I mean, go back and play with it again) and see if I can recreate whatever the problem was. But it'll be sometime next week before I have a chance
I'm going to push a Mono update for F-11, synchronizing it with Rawhide's mono 2.4.2.3, and currently MDB files are still being shipped with the -core RPM. What's the status of the find-debuginfo.sh work? I'll probably push the update out anyway, unless we can land the debugging changes soon-ish.