I was always though that the debug USE flag is for adding debugging symbols, but based on discussion in http://forums.gentoo.org/viewtopic-p-5301559.html#5301559 and documentation http://www.gentoo.org/proj/en/qa/backtraces.xml it is not true.
Could be possible to automatically add the "nostrip splitdebug" FEATURES when the debug flag is enabled? Or is there any other way, how to permanent enable these features to only some packages? E.g. qt:4 and kde:4?
USE=debug is not supposed to be used by most users, since it enables debug codepaths that usually can lead to:
- slower code;
- code that aborts on mistakes instead of handling them "nicely"; (assertions)
- code that produces debug output (in the case of nano, making the editor mostly useless);
So the meaning of the two have to stay separated.
As for "nostrip splitdebug", the latter is enough, so it's just FEATURES=splitdebug, and at that point it's simpler to just enable it system-wide. On a system with 1369 packages, my /usr/lib/debug is just shy of 5GB, but this is also having -ggdb enabled for all of them.
$ euse -I debug
[- ] debug - Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see http://www.gentoo.org/proj/en/qa/backtraces.xml
Problem is that I never before have an idea to check what the debug USE flag really means :-(
I don't want to enable the splitdebug FEATURE globally - I have only 6GB in /usr free on my laptop now. Bud in another issue with Amarok2, mysql and -fPIC flag is a solution how to set some environment variables locally with newest portage.
# cat /etc/portage/env/kde-base/kate
I've created such file for all important packages (qt-, kdelibs, kate...) and now I'm recompiling these packages. After recompiling of all qt- packages, the debug directory has 480MB. Will see the kdelibs result.
Maybe should be this solution also included in the documentation.
Don't see anything for QA to do here...