Hi. While trying to build ufraw gimp plugin, emerge failed saying: * to enable gimp support, you must enable gtk support I have gtk USE flag off globally, as I prefer Qt (when there is a choice ...) This forces me to add an exception for ufraw into package.use, which I don't like (each bit diverging from the default configuration increases the maintenance pain) and seems quite unnecessary for me - if gimp support is explicitly requested, and gtk is a pre-requisite for it, then it should be autoenabled. I've already seen this behaviour with some ebuilds before, please make my life easier (well, hopefully not just mine :-)) also with this one. Reproducible: Always Steps to Reproduce: 1. USE="gimp -gtk" emerge ufraw Actual Results: Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) media-gfx/ufraw-0.16 * ufraw-0.16.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * to enable gimp support, you must enable gtk support * * ERROR: media-gfx/ufraw-0.16 failed. ... Expected Results: Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) media-gfx/ufraw-0.16 * ufraw-0.16.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * * WARN: gimp enabled, autoenabling gtk * >>> Unpacking source... ... While we may argue that while GIMP is explicitly enabled, GTK is explicitly disabled, and so emerge could not decide which should take preference, I think the common concept of dependency solving is to pull in the minimal set of things needed to satisfy the demand for things selected to be installed, not to disable to install things that need things which wouldn't be pulled in otherwise.
fixed in cvs, thanks for the suggestion. 28 Dec 2009; Markus Meier <maekke@gentoo.org> ufraw-0.16.ebuild: autoenable gtk when gimp is enabled, bug #298187
thanks!
