A few comments about this proposal. We have an existing convention for naming arbitrary property values. This is used for the attribute action, and is how we store attributes in a manifest. Check out src/modules/actions/attribute.py for the code.
> [attribute] > title = "..." > uuid = "..." This would instead look something like <attribute identifier> name = "title" value = "..." <attribute identifier> name = "uuid" value = "..." > With both of these issues, the intent is to be able to store some > per-image attribute data, especially for user images. This data will be > stored in the cfg_cache file in a new section: We intend to blow-up the cfg_cache in the fullness of time. It might be worthwhile to think about other ways of storing these attributes. Are you going to have a lot of these things? -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
