Bug 472092 – gnome2.eclass: catch ebuilds don't setting GCONF_DEBUG="no"

• Status: RESOLVED DUPLICATE of bug 270919
• Product: Gentoo Linux

[Description Pacho Ramos 2013-06-02 12:26:23 UTC]

There are lots of ebuilds forgetting to even set GCONF_DEBUG and, then, leading to a "debug" flag being added even if they don't have "--enable-debug" toggle, but they are hard to catch because the configure option is passed only when debug USE if enabled

Attached patch adds a check for fixing this cases

Reproducible: Always

[Comment 1 Pacho Ramos 2013-06-02 12:26:38 UTC]

Created attachment 349900 [details, diff]
1.patch

[Comment 2 Pacho Ramos 2013-06-03 20:12:42 UTC]

I have just seen this case -> gnome-bluetooth-3.8.1

It has GNOME_DEBUG_CHECK in configure.ac... but it leads to a normal --enable/disable-debug (without yes/no/minimum). What needs to be done in that cases? Set GCONF_DEBUG="no" and handle it normally? (with $(use_enable debug))

[Comment 3 Pacho Ramos 2014-11-03 16:17:16 UTC]

(In reply to Pacho Ramos from comment #2)
> I have just seen this case -> gnome-bluetooth-3.8.1
> 
> It has GNOME_DEBUG_CHECK in configure.ac... but it leads to a normal
> --enable/disable-debug (without yes/no/minimum). What needs to be done in
> that cases? Set GCONF_DEBUG="no" and handle it normally? (with $(use_enable
> debug))

I guess that it should handle it manually and, instead, if we decide to keep GCONF_DEBUG for the "special" handling, it should either pass --enable-debug or --enable-debug=minimum. That way we also catch the (many) packages that shouldn't really use this switch

[Comment 4 Pacho Ramos 2015-12-16 12:07:08 UTC]

Well, as this cannot be really done, better wait for rethinking all this debugging stuff in bug 270919 (hopefully for eapi6)

*** This bug has been marked as a duplicate of bug 270919 ***

[Comment 5 Gilles Dartiguelongue (RETIRED) 2015-12-17 08:17:13 UTC]

I have a patch laying somewhere to add eqawarn when the variable is unset. Of course, this EAPI bump is a nice way to act on it too.