-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 25/07/14 04:12 PM, Pacho Ramos wrote:
> El vie, 25-07-2014 a las 15:54 -0400, Ian Stakenvicius escribió:
>> On 25/07/14 03:51 PM, Pacho Ramos wrote:
>>> El vie, 25-07-2014 a las 20:46 +0100, Ciaran McCreesh
>>> escribió:
>>>> On Fri, 25 Jul 2014 21:44:02 +0200 Luis Ressel
>>>> <ara...@aixah.de> wrote:
>>>>> Okay, I didn't think of that. I'm not sure if the blocker
>>>>> deps or the REQUIRED_USE would be more helpful for Portage,
>>>>> but generally I think that the REQUIRED_USE error message
>>>>> is quite hard to understand for unexperienced users -- much
>>>>> more so than the error generated by a blocker dep.
>>>>
>>>> ...and the fix for that is to scrap REQUIRED_USE and use
>>>> pkg_pretend instead.
>>>>
>>>
>>> Could you give an example to let us see how pkg_pretend could
>>> be used to achieve the same as REQUIRED_USE?
>>>
>>> Thanks
>>>
>>>
>>
>> pkg_pretend() { if use heimdal && use mit-krb5; then eerror
>> "Please set only one of the use following flags:" eerror
>> "heimdal, mit-krb5" die "conflicting use flags set" fi }
>
> Ah, ok, I was wondering why REQUIRED_USE was implemented then :/,
> I guess it was for simplifying ebuilds?
>
>
REQUIRED_USE came first, pkg_pretend came later, iirc. In theory,
REQUIRED_USE could have made a nice interactive way to resolve use
conflicts, it just never did.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iF4EAREIAAYFAlPSyG4ACgkQ2ugaI38ACPC07wD/VnEG/w0nvYlNsVJszyPXgK0l
Z9YZ3zWOeMffAJiM7NQBAI8x5G5+EXgCrd8gGAA20ENZ5RIuN6qJoE1INRY6x84+
=6L9c
-----END PGP SIGNATURE-----
