[EMAIL PROTECTED] wrote: > 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? > No. Although we would also like to see the convention of supporting a "description"property. The description would be initialized by distro assemblers as they create the image at the factory, displayed by the package manager/update tool GUIs and modified by users if they so desire.
Tom, since the "title" is of the same ilk as the "summary" attribute on packages, how about referring to the title as "summary" and, similarly, using "description" for the optional paragraph description of the image? Thanks, Chris > -j > > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
