-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/08/15 01:38 PM, Ulrich Mueller wrote: >>>>>> On Wed, 12 Aug 2015, Ciaran McCreesh wrote: > >> The opposing viewpoint was ferringb believing he could do >> "automatic dependency resolution" for a build server setup, >> without trying it and without an implementation, and that a >> human-readable pkg_pretend would somehow preclude that. > > Hm, how about adding a new PM command like "required_use foo > -bar"? It would be used exclusively in pkg_pretend, and tell the > PM to suggest the necessary package.use changes to the user (or > even update them automatically with the appropriate > --autounmask-* option). > > REQUIRED_USE could be banned at the same time. > > Ulrich >
That's an interesting idea.... from the PM perspective do we have any functions that can directly affect deptree calculations now? Crossing that line is the only thing I forsee right now as being the main issue with this one. Would the 'required_use' function just suggest/set/force the necessary change or would it perform the logic too? ie, would we just call 'required_use foo -bar', or would we: 'if use foo && use bar ; then required_use foo -bar ; fi' ? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlXLhpgACgkQAJxUfCtlWe0bXwEAtDn5LL2VE0xBJqVxQ193kPeo Wn8sm6ud5YgUA2hJkBMA/0IDzi4hg7UZsnqdw59m/DGiYE6Devlfo4LoactUVpDD =4bED -----END PGP SIGNATURE-----
