evolution 1.2 and above, which can now use openssl for it's ssl support will still require mozilla even if the use flags say otherwise. The ebuilds for 1.2.0 and 1.2.1 clearly show the desired behavior: # ssl? ( mozilla? ( >=net-www/mozilla-0.9.9 ) ) # ssl? ( !mozilla? ( >=dev-libs/openssl-0.9.5 ) ) # This is how the deps should be, but portage cannot handle it The most reasonable thing to do in this case would be to have drop the ssl use flag generating a dependency on mozilla since the ebuild logic would only use openssl in that case anyway and everything would work as expected.
fixed in cvs. the new DEPEND line uses nested USE flags which i've tested with portage-2.0.47-r7. only fixed in 1.2.2. hopefully there'll be enough testing for this to go stable soon during the thaw ..
