| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 25/07/14 04:12 PM, Pacho Ramos wrote: |
| 5 |
> El vie, 25-07-2014 a las 15:54 -0400, Ian Stakenvicius escribió: |
| 6 |
>> On 25/07/14 03:51 PM, Pacho Ramos wrote: |
| 7 |
>>> El vie, 25-07-2014 a las 20:46 +0100, Ciaran McCreesh |
| 8 |
>>> escribió: |
| 9 |
>>>> On Fri, 25 Jul 2014 21:44:02 +0200 Luis Ressel |
| 10 |
>>>> <aranea@×××××.de> wrote: |
| 11 |
>>>>> Okay, I didn't think of that. I'm not sure if the blocker |
| 12 |
>>>>> deps or the REQUIRED_USE would be more helpful for Portage, |
| 13 |
>>>>> but generally I think that the REQUIRED_USE error message |
| 14 |
>>>>> is quite hard to understand for unexperienced users -- much |
| 15 |
>>>>> more so than the error generated by a blocker dep. |
| 16 |
>>>> |
| 17 |
>>>> ...and the fix for that is to scrap REQUIRED_USE and use |
| 18 |
>>>> pkg_pretend instead. |
| 19 |
>>>> |
| 20 |
>>> |
| 21 |
>>> Could you give an example to let us see how pkg_pretend could |
| 22 |
>>> be used to achieve the same as REQUIRED_USE? |
| 23 |
>>> |
| 24 |
>>> Thanks |
| 25 |
>>> |
| 26 |
>>> |
| 27 |
>> |
| 28 |
>> pkg_pretend() { if use heimdal && use mit-krb5; then eerror |
| 29 |
>> "Please set only one of the use following flags:" eerror |
| 30 |
>> "heimdal, mit-krb5" die "conflicting use flags set" fi } |
| 31 |
> |
| 32 |
> Ah, ok, I was wondering why REQUIRED_USE was implemented then :/, |
| 33 |
> I guess it was for simplifying ebuilds? |
| 34 |
> |
| 35 |
> |
| 36 |
|
| 37 |
|
| 38 |
REQUIRED_USE came first, pkg_pretend came later, iirc. In theory, |
| 39 |
REQUIRED_USE could have made a nice interactive way to resolve use |
| 40 |
conflicts, it just never did. |
| 41 |
|
| 42 |
|
| 43 |
-----BEGIN PGP SIGNATURE----- |
| 44 |
Version: GnuPG v2 |
| 45 |
|
| 46 |
iF4EAREIAAYFAlPSyG4ACgkQ2ugaI38ACPC07wD/VnEG/w0nvYlNsVJszyPXgK0l |
| 47 |
Z9YZ3zWOeMffAJiM7NQBAI8x5G5+EXgCrd8gGAA20ENZ5RIuN6qJoE1INRY6x84+ |
| 48 |
=6L9c |
| 49 |
-----END PGP SIGNATURE----- |
Archives