On Wed, Apr 30, 2008 at 3:21 PM, Darren J Moffat <[EMAIL PROTECTED]> wrote: > Brad Vaughan wrote: > > Depending on the intended use of the metadata (ie. end user > > functionality/management/maintenance vs. development vs. system ) and > > the ease of maintenance, the information types could be dramatically > > different. I am going to assume the initial intended use is not end-user > > related and difficult to maintain so I think initially we would limit to > > a single attribute. > > So it it isn't end-user related and it is difficult to maintain maybe it > isn't the correct solution to the problem. > > BTW what is the real problem here ? I don't think it is that the pkg > repository is not "network" rather than on a CD but that there needs to > be a way to determine where given installed bits came from.
In theory, that's as easy as: pkg search /path/to/bits Then you could use pkg info to get the service attributes, etc. ? > > If I am wrong on my assumptions, then there are other data types that > > would be useful for system management and support purposes. > > I worked in support (Sun Service) and not once did I ever look at the > information in a package to determine if a command/utility/etc was > supported. So I see little value in this metadata in a package based on > my personal experience. pkg bitsaresupported /path/to/bits anyone? :-) -- Shawn Walker "To err is human -- and to blame it on a computer is even more so." - Robert Orben _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
