"core-os" seems like it might end up being overly broad, given that, at least at the moment, it covers the entire WOS.
How is "minimal" defined? Is it hardcoded to a list of packages somewhere? It seems to me that you might as well make the leap to allowing package names (or patterns) for the group, and replace "minimal" with some well-known package name that defines the minimal set of packages, and "core-os" with the incorporations that carry those attributes. Or maybe not ... ? "sync" and "mirror" act very much like "incorporate" and "require" do for dependencies (though the versioning for the depend actions isn't exact). I wonder if there's some convergence, either in terminology or in mechanism, that could be done here. I'm not sure that sync and mirror really say what you want them to, but perhaps I've been drinking the pkg(5) terminology kool-aid for too long. Will administrators in the zone be able to modify these policies? Typically "image properties" are stored in the image, and not external to the image, which means that zone admins could violate policy set by gz admins. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
