On Thursday 30 October 2008 12:04:27 Ciaran McCreesh wrote: > 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.
I think we should only phase out *.local.conf. Adding descriptions for say every lingua via an exlib gets messy and writing it out everywhere is too much duplication. We should require a description for everything either via global descriptions or annotations. > 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? I have yet to see a case where it's needed. Could also be implemented via ( -flag ) [[ requires = [ ... ] ]] ? > Did we also want [[ default = enabled|disabled ]] ? I'd rather have better options.conf in profiles and keep it in one place (per repo) which handles forced, masked and default options. > 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? I'd say implement that. > 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? I think it would be nice at least. mplayer for instance have seven options that require the X options. [...] > Anything else I've missed? Would it be nice to be able to provide explanations for option requirements? -- Bo Andresen
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Exherbo-dev mailing list [email protected] http://lists.exherbo.org/mailman/listinfo/exherbo-dev
