Currently we have: flag [[ description = [ blah ] ]]
This has priority over any desc file. Someone should decide whether
we're phasing out desc files entirely, whether we want descriptions for
every option on every package and so on.
We need to work out exactly how to do requirements. I'm thinking along
the lines of:
flag [[ requires = [ foo bar -baz ] ]]
Do we also need requires-if-unset?
Did we also want [[ default = enabled|disabled ]] ?
For inter-flag dependencies, we were talking about adding in groups
with annotations:
( foo bar baz ) [[ number-selected = exactly-one ]]
where exactly-one might also be at-most-one or at-least-one. Should I
implement this, or is there anything else to add?
There was talk of allowing requires on groups too, as a shortcut. So
you'd have this:
( flag1 flag2 ) [[ requires = [ foo bar -baz ] ]]
Given that this is purely a shortcut, do we really want it?
We also have to deal with situations like this now:
foo [[ description = [ The foo ] ]]
foo [[ requires = monkey ]]
bar [[ description = [ The bar ] ]]
( foo bar [[ requires = monkey ]] ) [[ number-selected = exactly-one ]]
Currently we merge together every annotation key from every mention of
a flag, and warn and take an arbitrary value if there're duplicates. Do
we instead want to define specific behaviour for duplicate keys?
Anything else I've missed?
--
Ciaran McCreesh
signature.asc
Description: PGP signature
_______________________________________________ Exherbo-dev mailing list [email protected] http://lists.exherbo.org/mailman/listinfo/exherbo-dev
