Bug 160115 – x11-libs/gtk+ : please remove debug.eclass usage

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Diego Elio Pettenò (RETIRED) 2007-01-04 14:52:17 UTC]

The following ebuilds/eclasses currently inherits debug.eclass:

./x11-libs/gtk+/gtk+-2.8.12.ebuild:inherit gnome.org flag-o-matic eutils debug autotools
./x11-libs/gtk+/gtk+-2.8.19.ebuild:inherit gnome.org flag-o-matic eutils debug autotools virtualx
./x11-libs/gtk+/gtk+-2.8.20-r1.ebuild:inherit gnome.org flag-o-matic eutils debug autotools virtualx
./x11-libs/gtk+/gtk+-2.8.8.ebuild:inherit gnome.org flag-o-matic eutils debug
./x11-libs/gtk+/gtk+-2.10.6.ebuild:inherit gnome.org flag-o-matic eutils debug autotools virtualx

As per bug #55708 you can see that the current debug.eclass is a QA mess, and I'm going to replace it soon with a dummy version.
The debug useflag should not mess with the user's *FLAGS, but rather relate to the debug codepaths of a package (asserts, extra output, and so on). If an user wants a debuggable system, he should follow the backtraces guide (http://www.gentoo.org/proj/en/qa/backtraces.xml) that contains all the needed info.

For this reason, please remove debug eclass from inherit line, add debug to IUSE if your package has a way to enable/disable debug codepaths, and set this bug resolved. Please do it for _every revisions of your package_.

Thanks,
Diego

[Comment 1 Diego Elio Pettenò (RETIRED) 2007-01-04 20:48:30 UTC]

Fixed.

[Comment 2 Diego Elio Pettenò (RETIRED) 2007-01-04 20:58:21 UTC]

Reopen per compnerd's request.

[Comment 3 Mart Raudsepp 2007-01-08 05:44:58 UTC]

For information:
The request to have the bug open still, was to check that all the debug codepaths are enabled in the package with USE=debug (the extra asserts, debugging facilities and so on inside gdb - not debugging symbols)

[Comment 4 Mart Raudsepp 2007-01-14 16:44:24 UTC]

The debug paths seem to work good by my testing. Closing this now