NEW: Solaris Package Companion v0.7
By gbrunett-Oracle on Nov 02, 2007
The Solaris Package Companion is a small Korn shell script that allows you to ask quite a number of interesting questions about the relationships between Solaris metaclusters, clusters and packages as well as their respective dependencies. Very often, answers to these kinds of questions are essential for the construction of minimized systems as well as more generally for OS golden images. The goal of the Solaris Package Companion, or SPC for short, is to do all of the hard work so you don't have to. SPC will create a cache of important facts by mining information from the various packaging files and directories to allow you to quickly and easily obtain answers to a variety of questions such as: \* What clusters or packages are contained in a given metacluster? \* What packages are contained in a given cluster? \* What metacluster or cluster contains a given package? \* On what other packages does a given package or cluster depend? \* Which packages depend on a given package? \* … and so on…
New to this release is the tag before the item description to inform the user of the type of object being dispayed. [P] indicates a package while [C] is a cluster and [M] is a metacluster. Another new feature is the ability to fold packages back into their respective clusters (where possible). This can be helpful when trying to create a complete list of items for a standard OE image or JumpStart configuration. Essentially, this will report the cluster name in which the package is found. This can be accomplished using the -F (folding) option. The new -Z option will display the list of packages that depend on a specific cluster. There is also an new experimental option -f that will allow you to map a file to a package or cluster (with the -F option). This only works for local files reliably right now. Finally, special thanks to Dave Comay for reporting a bug - that has been fixed in this version too!
You can find more information, examples and the source code on the project page.