The lablgtk-2.4.0 ebuild tests whether USE=gnome is set, and if it is not, then it provides the configure flags "--without-gnomecanvas --without-gnomeui --without-panel" when building the library. That's not necessarily a good idea, IMHO, because you can have gnomecanvas installed without having USE=gnome set, and lablgtk can use gnomecanvas without the other components installed just fine. IMHO, the ebuild should specify --with-xxx flags in case USE=gnome is set, not the other way round. Reproducible: Always Steps to Reproduce: 1. emerge gnomecanvas 2. USE=-gnome emerge labgtk Actual Results: lablgtk is installed without support for gnomecanvas. Expected Results: It should have support for gnomecanvas. ;-)
Is there anything happening because of this report? Will the ebuild be changed? Or not? Just wondering because it has been a couple of months ...
No, it should not include it if not specified (I would do it if we had choice as maintainers to set/unset a particular flag by default in the ebuild, but we cannot as of now). If we did that there would be no way to remove support to e.g. gnomecanvas when gnome is installed (see bug #100164). Note that 2.2.0 still use autodetection but it will be removed soon.
How about adding another USE flag for gnomecanvas then? Gnome is one darn big package; I bet I'm not the only person who has some libraries installed and some not. "on/off" of the entire thing is not enough granularity, IMHO.
I added a new gnomecanvas flag, gnomeui depends on it and i see no point having gnomeui without gnomepanel. Hope this fits your needs ;)
Yes, it does. Thank you.
