| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 12/08/15 09:40 AM, Michael Orlitzky wrote: |
| 5 |
> At the very least, we need to be able to tag REQUIRED_USE |
| 6 |
> conflicts with human readable error messages. OK, so I know I |
| 7 |
> can't have USE="qt4 qt5" for this package... but why? How do I |
| 8 |
> fix it? We can do that with pkg_pretend and a bunch of "if" |
| 9 |
> statements, or maybe there's value in having the requirements in |
| 10 |
> a variable -- who knows. The former is a lot simpler to |
| 11 |
> implement. |
| 12 |
> |
| 13 |
> |
| 14 |
|
| 15 |
I still think it's really important to note the meaning of "Can't" |
| 16 |
here. "Can't" IMO should still really mean cannot -- that setting |
| 17 |
both flags is going to cause a problem that'll break the system, |
| 18 |
conflicts that will cause things to not work. This whole qt4/qt5 |
| 19 |
discussion isn't about "can't", but about "doesn't." |
| 20 |
|
| 21 |
|
| 22 |
-----BEGIN PGP SIGNATURE----- |
| 23 |
Version: GnuPG v2 |
| 24 |
|
| 25 |
iF4EAREIAAYFAlXLWoAACgkQAJxUfCtlWe2GAwD/dgkq8Iyd4njMd2tAvO8zWVOr |
| 26 |
JddKwKnUxMxT4haGYDYBAIxIQbT5BM3+iHkNWXF8nKm6GXukNKqUODhZl3eNRoUi |
| 27 |
=kAZd |
| 28 |
-----END PGP SIGNATURE----- |
Archives