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