Ticket #956 (new enhancement)

Opened 10 years ago

Last modified 9 years ago

auto-resolution of MYOPTIONS deps

Reported by: zlin Owned by:
Priority: Sometime Milestone: cave Long Term Extras
Component: clients/cave Version: scm
Keywords: Cc:
Blocked By: Blocking:
Distribution: Exherbo


Which could be used by the next gimme.rb too

Change History

comment:1 Changed 9 years ago by ciaranm

We *could* do this by rewriting MYOPTION requirements into self-run-deps. However, it's not clear how we'd proceed. Do we just go for the leftmost? Or do we flag things as being 'primary' for auto-resolution in some way? Do we only auto-resolve things flagged that way?

Given a require-exactly-one of a b c d e, where b and c are enabled, do we disable c?

Given a require-exactly-one of a b c d e, none are enabled, do we enable a?

What happens if things are inside a foo? ( ) block?

Bear in mind that if there're three or more flags, there's no algorithm in P that'll always work...

Note: See TracTickets for help on using tickets.