Bart, My original reaction to this was "Oh, great. Two more IPS specific concepts I need to get my head around". But after thinking about it I'm hoping this ends up getting mapped in a general fashion to the (possibly enhanced) tag/filter mechanism.
Is the intent to define a new syntax for specifying facet/variant "filters"? I.e. something like this (using cfg_cache): [selector] variant.arch=sparc facet.locale=en_US.UTF-8 I'd be concerned with that. This is ambiguous, and requires that you understand how variants and facets work and interact in order to know what this "filter" does. I'd prefer building off the existing tag/filter syntax like this: [filter] variant.arch=sparc & facet.locale ~ en_US.UTF-8 where facet.locale is a tag with a list value and "~" means contains (or overload "=" if that was deemed more appropriate). These would be enhancements to the current tag/filter implementation. This is more explicit which I like, and variants and facets become ways of using tags as opposed to entirely new things with their own behavior and syntax. Joe Bart Smaalders wrote: > I've updated my facet/variant notes based on our discussion. > Highlights of the changes: > > * L10n facets are now done in the form facet.l10n=en_US > rather than facet.l10n.en_US=true. > * facets are now ANDED together as well if the names are > different. > * facet hierarchies and wild-carding are supported. > > Package facets and variants > --------------------------- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
