-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 13/08/15 04:24 AM, Sergey Popov wrote: > 11.08.2015 17:56, Ian Stakenvicius пишет: >> BUT I would advise against this. If a user has specified both >> qt4 and qt5 in USE, then I see no problem with the VDB having >> both qt4 and qt5 atoms listed as dependencies. End-users that >> want a clean VDB can just make sure they only enable one flag, >> but end-users that don't care will have packages that just >> work. >> > > great, in that case emerge --depclean becomes completely > useless, because of unneeded vdb deps. Those DEPENDs that i have > provided was at least consistent in terms of dependencies(that > does not mean that they are not ugly, though) >
No it doesn't. It's true that it doesn't end up providing a necessarily fully clean system when both flags are enabled, but there's nothing to keep end-users (or the profiles, when they change) from disabling the qt4 flag on their own terms to get a cleaner system. My entire point here is using the BFH of REQUIRED_USE to force end-users to take manual action on emerge, just because some dev's want them to have a cleaner system via --depclean, -especially- when there aren't any conflicts between the qt4 and qt5 deps being installed at the same time, is to the detriment of end users much more than the extra libs in the system image. If qt4 and qt5 libs collided or conflicted, then this would be a different story, but they don't. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlXMqToACgkQAJxUfCtlWe3tDgEAjPRuf+zAFhYWYNyLefIptPnT 0y3Z2UuOIBO2Bdmqp1oBAJgIMpH5c95dKXkskL/UzvYhgdG4Z8vPDbCjKc/NMZ8g =j8+H -----END PGP SIGNATURE-----
