Wiki code for Solaris Package Companion

Hide Line numbers
1: == Solaris Package Companion
2: 
3: 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.
4: 
5: 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:
6: 
7: * What clusters or packages are contained in a given metacluster?
8: * What packages are contained in a given cluster?
9: * What metacluster or cluster contains a given package?
10: * On what other packages does a given package or cluster depend?
11: * Which packages depend on a given package?
12: * ... and so on...
13: 
14: Note that this tool is provided to the community for its use, but it is not officially supported by Sun.
15: 
16: === Acknowledgements
17: 
18: Thank you to all of the people who given this tool a try!  As of March 2009, the Solaris Package Companion has been downloaded over 4,500 times!
19: 
20: I also want to publicly thank the following people who have contributed to this project:
21: 
22: * Jerome Blanchet.  For providing a patch to include support for processing of reverse dependency declarations in "depend" files and for providing a patch to improve the processing and display of platform dependent packages.
23: * Dave Comay.  For reporting a bug related to an unanchored grep operation.
24: * Clive King.  For pointing out a bug related to the processing of local system package information.
25: * Fredrich Maney.  For contributing the tree display output mode.
26: * Peter Pickford.  For pointing out a case where not all package dependencies were being captured.
27: 
28: === Downloading the Tool
29: 
30: The current version of the Solaris Package Companion is [[v0.9>>http://mediacast.sun.com/users/gbrunette/media/spc-v0.9]].  The MD5 fingerprint for this file is: 
31: 
32:      $ **digest -v -a md5 ./spc-v0.9.ksh**
33:      md5 (./spc-v0.9.ksh) = 0df57f4e0a1cbeea62e3873d1949916c
34: 
35: An older [[version>>http://mediacast.sun.com/users/gbrunette/media/spc-v0.8.1]] of the tool is available in case there are any problems with the current version.  The MD5 fingerprint for version 0.8.1 is:
36: 
37:      blackhole$ **digest -v -a md5 ./spc-v0.8.1.ksh**
38:      md5 (./spc-v0.8.1.ksh) = 7bf5831685562b62dce1cc0304b3d720
39: 
40: The information below assumes that you are using the latest version of the tool.
41: 
42: === Installing the Tool
43: 
44: The Solaris Package Companion is just a single shell script and can be installed into any directory location.  Permissions typically should be:
45: 
46: {{{
47:     $ **ls -l spc-v0.9.ksh**
48:     \-rwxr-xr-x   1 gbrunett staff      24841 Aug  1 14:55 spc-v0.9.ksh
49: }}}
50: 
51: === Using the Tool
52: 
53: The following is the list of options supported by the Solaris Package Companion:
54: 
55: {{{
56:     $ **./spc\-v0.9.ksh \-h**
57:     General Options:
58:        \-F           [fold packages into their respect clusters - experimental]
59:        \-h, -?       [show help]
60:        \-l           [local mode - use local system repositories and data]
61:        \-r           [repository location]
62:        \-s           [solaris distribution location]
63:        \-v           [show package details]
64:     Processing Options:
65:        To initialize the information repository used by this tool.
66:           \-i (used with either the -s or -l options)
67:        To display the list of packages contained in the specified cluster(s).
68:           \-c <package cluster list>
69:        To display the metacluster(s) that contain the specified cluster(s).
70:           \-C <package cluster list>
71:        To display the dependencies for the specified package(s).
72:           \-d <package list>
73:        To display the dependencies for the specified cluster(s).
74:           \-D <package cluster list>
75:        To evaluate install packages on a system against a specified metacluster.
76:           \-e <metacluster>
77:        To determine what package contains a given file (experimental).
78:           \-f <file name> (fully qualified path names only)
79:        To display the packages contained in the specified metacluster(s).
80:           \-m <metacluster list>
81:        To display the clusters contained in the specified metacluster(s).
82:           \-M <metacluster list>
83:        To display the cluster that contains the specified package(s).
84:           \-p <package list>
85:        To display the metacluster(s) that contain the specified package(s).
86:           \-P <package list>
87:        To display a tree view of the specified cluster(s) (experimental).
88:           \-t <cluster list>
89:        To display a tree view of the specified metacluster(s) (experimental).
90:           \-T <metacluster list>
91:        To display the list of packages that depend on the specified package(s).
92:           \-z <package list>
93:        To display the list of packages that depend on the specified cluster(s).
94:           \-Z <package cluster list>
95: }}}
96: 
97: Before you can use the tool for the first time, you must create its package information cache.  By default, the information cache contains 
98: information regarding packaging relationships, dependencies, names and even which files are contained within each package.  Collecting this amount of information can generate a cache of over 30M and take several minutes to complete.
99: 
100: If you are sure you do not need this much information, you can adjust one of the COLLECT_ variables inside of the program.  For each of these variables, the tool will automatically honor a pre-existing value (obtained from the shell or command line).  If no pre-existing value is defined, each of the COLLECT_ variables default to an "on" (1) value.  The smallest cache (created when the COLLECT_ variables are set to "off" (0)) is roughly 4MB.  In general, it is recommended that the settings remain unmodified so that the complete set of functionality is enabled.  Note that the repository need only be created once (for each distribution you want to inspect) so the impact should be minimal both in terms of time and disk space.
101: 
102: The information cache can be created in one of two ways depending on what you would like to accomplish.  First, if you would like to create a cache based on Solaris installation media, then you should use the following command:
103: 
104:      $ **./spc-v0.9.ksh -i -s /media/SOL_11_X86/Solaris_11/Product -r ./myrepository**
105: 
106: This will create a cache based on the Solaris OS media found at the location specified by the {{code}}-r{{/code}} option.  On the other hand, if you wanted to create a cache based upon the local system, you can use the following command:
107: 
108:      $ **./spc-v0.9.ksh -i -l -r ./myrepository**
109: 
110: In this case, it leverages information found on the currently installed system to create its cache (stored in ./myrepository).  Note that since each cache is specified by name, there is nothing to stop you from having multiple caches for different systems, versions of the operating system, etc.
111: 
112: The time to create the cache will vary depending on the media being read as well as the performance of the system on which it is being created.  Initial testing showed that the time could range from 10 to 30 minutes.  Once the cache is created, it will not need to be created nor modified again so this is a one time penalty as noted above.
113: 
114: === Examples
115: 
116: The following are just a few examples to illustrate how the SPC tool can be used to answer some very interesting packaging questions.  We would love to hear about other uses and requirements in this space, so please forward your ideas and feedback along!
117: 
118: Each of these examples was generated using the most recent version of the tool against a Solaris 10 05/08 (Update 5, build 10) repository.  Each of these examples should work with other versions of the Solaris OS including newer Nevada builds.
119: 
120: ==== What packages are in cluster SUNWCssh?
121: 
122: {{{
123:     $ **./spc-v0.9.ksh -r ./myrepository -c SUNWCssh**
124:     SUNWsshcu
125:     SUNWsshdr
126:     SUNWsshdu
127:     SUNWsshr
128:     SUNWsshu
129: }}}
130: 
131: In addition, you can always get more information by specifying the {{code}}-v{{/code}} option:
132: 
133: {{{
134:     $ **./spc-v0.9.ksh -v -r ./myrepository -c SUNWCssh**
135:     [P] SUNWsshcu                 SSH Common, (Usr)
136:     [P] SUNWsshdr                 SSH Server, (Root)
137:     [P] SUNWsshdu                 SSH Server, (Usr)
138:     [P] SUNWsshr                  SSH Client and utilities, (Root)
139:     [P] SUNWsshu                  SSH Client and utilities, (Usr)
140: }}}
141: 
142: Updated in this release is the tag before the item name 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.  In previous releases this was placed between the item name and item description.
143: 
144: Also new in this release is the ability to display information in a tree view.
145: 
146: ==== What packages are in cluster SUNCssh (tree view)?
147: 
148: {{{
149:     $ **./spc-v0.9.ksh -v -r ./myrepository -t SUNWCssh**
150:        [C] SUNWCssh                  Secure Shell
151:           [P] SUNWsshcu                 SSH Common, (Usr)
152:           [P] SUNWsshdr                 SSH Server, (Root)
153:           [P] SUNWsshdu                 SSH Server, (Usr)
154:           [P] SUNWsshr                  SSH Client and utilities, (Root)
155:           [P] SUNWsshu                  SSH Client and utilities, (Usr)
156: }}}
157: 
158: Similar questions can be asked of metaclusters as well:
159: 
160: {{{
161:     $ **./spc-v0.9.ksh -v -r ./myrepository -T SUNWCmreq | head -10**
162:     [M] SUNWCmreq                 Minimal Core System Support
163:        [C] SUNWCfca                  Sun ISP Fibre Channel Device Drivers
164:           [P] SUNWqlc                   Qlogic ISP 2200/2202 Fibre Channel Device Driver
165:           [P] SUNWemlxs                 Emulex-Sun LightPulse Fibre Channel Adapter (FCA) driver (root)
166:        [C] SUNWCfct                  Sun Fibre Channel Transport Software
167:           [P] SUNWfcsm                  FCSM driver
168:           [P] SUNWfctl                  Sun Fibre Channel Transport layer
169:           [P] SUNWfcp                   Sun FCP SCSI Device Driver
170:           [P] SUNWfcip                  Sun FCIP IP/ARP over FibreChannel Device Driver
171:        [C] SUNWCfmd                  Fault Management Daemon and Utilities
172:     [...]
173: }}}
174: 
175: ==== In what metaclusters is the SUNWsshdr package found?
176: 
177: {{{
178:     $ **./spc-v0.9.ksh -v -r ./myrepository -P SUNWsshdr**
179:     [M] SUNWCall                  Entire Distribution
180:     [M] SUNWCprog                 Developer System Support
181:     [M] SUNWCuser                 End User System Support
182:     [M] SUNWCXall                 Entire Distribution plus OEM support
183: }}}
184: 
185: ==== On what packages does the SUNWsshdu package depend?
186: 
187: {{{
188:     $ **./spc-v0.9.ksh -v -r ./myrepository -d SUNWsshdu**
189:     [P] SUNWcakr                  Core Solaris Kernel Architecture (Root)
190:     [P] SUNWcar                   Core Architecture, (Root)
191:     [P] SUNWckr                   Core Solaris Kernel (Root)
192:     [P] SUNWcnetr                 Core Solaris Network Infrastructure (Root)
193:     [P] SUNWcsd                   Core Solaris Devices
194:     [P] SUNWcsl                   Core Solaris, (Shared Libs)
195:     [P] SUNWcsr                   Core Solaris, (Root)
196:     [P] SUNWcsu                   Core Solaris, (Usr)
197:     [P] SUNWgss                   GSSAPI V2
198:     [P] SUNWgssc                  GSSAPI CONFIG V2
199:     [P] SUNWkvm                   Core Architecture, (Kvm)
200:     [P] SUNWopenssl-libraries     OpenSSL Libraries (Usr)
201:     [P] SUNWsshcu                 SSH Common, (Usr)
202:     [P] SUNWsshdr                 SSH Server, (Root)
203:     [P] SUNWzlib                  The Zip compression library
204: }}}
205: 
206: 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.  This can be accomplished using the ’-F’ (folding) option:
207: 
208: {{{
209:     $ **./spc-v0.9.ksh -v -r ./myrepository -d -F SUNWsshdu**
210:     [P] SUNWcakr                  Core Solaris Kernel Architecture (Root)
211:     [P] SUNWcar                   Core Architecture, (Root)
212:     [C] SUNWCcs                   Core Solaris
213:     [C] SUNWCfwcmp                Freeware Compression Utilities
214:     [C] SUNWCopenssl              OpenSSL
215:     [C] SUNWCssh                  Secure Shell
216:     [P] SUNWgss                   GSSAPI V2
217:     [P] SUNWgssc                  GSSAPI CONFIG V2
218:     [P] SUNWkvm                   Core Architecture, (Kvm)
219: }}}
220: 
221: In this case, several of the packages were able to be folded into their respective clusters leaving just a handful of individual packages.  These packages do not belong to any existing software cluster.
222: 
223: ==== Which package contains the file /usr/sbin/zic?
224: 
225: {{{
226:     $ **./spc-v0.9.ksh -r ./myrepository -l -v -f /usr/sbin/zic**
227:     [P] SUNWcsu                   Core Solaris, (Usr)
228: }}}
229: 
230: ==== Which package cluster contains the file /usr/sfw/lib/libcrypto.so?
231: 
232: {{{
233:     $ **./spc-v0.9.ksh -r ./myrepository -l -F -v -f /usr/sfw/lib/libcrypto.so**
234:     [C] SUNWCopenssl              OpenSSL
235: }}}
236: 
237: ==== Which packages depend on the SUNWmfrun package?
238: 
239: {{{
240:     $ **pkginfo SUNWmfrun**
241:     system      SUNWmfrun Motif RunTime Kit
242: }}}
243: 
244: {{{
245:     $ **./spc-v0.9.ksh -v -r ./myrepository -z SUNWmfrun | head -10**
246:     [P] IPLTadcon                 Administration Server Console
247:     [P] IPLTadmin                 Administration Server
248:     [P] IPLTcadcon                Administration Server Console Simplified Chinese Localization
249:     [P] IPLTcadmin                Administration Server Simplified Chinese Localization
250:     [P] IPLTccons                 Console Client Base Simplified Chinese Localization
251:     [P] IPLTcdscon                Directory Server Console Simplified Chinese Localization
252:     [P] IPLTcdsu                  Directory Server (usr) Simplified Chinese Localization
253:     [P] IPLTcons                  Console Client Base
254:     [P] IPLTdscon                 Directory Server Console
255:     [P] IPLTdsr                   Directory Server (root)
256: }}}
257: 
258: This option can also take advantage of the folding (-F) option to merge packages back into their respective clusters (if applicable):
259: 
260: {{{
261:     $ **./spc-v0.9.ksh -v -F -r ./myrepository -z SUNWmfrun | grep "~[C~]"**
262:     [C] SUNWCappserver            Sun Java(tm) System Application Server
263:     [C] SUNWCbrowser              SUNWCbrowser
264:     [C] SUNWCbrowserdev           SUNWCbrowserdev
265:     [C] SUNWCdhcp                 DHCPv4 Services
266:     [C] SUNWCdtdev                CDE Developer Software
267:     [C] SUNWCdtrun                CDE Runtime Software
268:     [C] SUNWCdtts                 Solaris Trusted Extensions CDE
269:     [C] SUNWCdtusr                CDE End User Software
270:     [C] SUNWCevo                  Evolution
271:     [C] SUNWCevodev               Evolution Developer Packages
272:     ...
273: }}}
274: 
275: === Testing the Tool 
276: 
277: After some reworking, I have also released version 0.1 of the Solaris Package Companion Testing Tool, [[spc-test-v0.1.sh>>http://mediacast.sun.com/users/gbrunette/media/spc-test]].  This tool is fairly configurable, allowing you to test multiple versions of the tool against multiple repositories.  There are currently 48 tests although tests can be easily added or removed as needed.  It can optionally display the results to the screen, but by default it records them in a directory where a basic consistency check is performed to detect differences in output (for the same repository) resulting from the use of different versions of the tool.  This is not intended to be an all encompassing test suite, but rather a basic sanity check to make sure the key functions are working as expected.
278: 
279: === Project Lead(s)
280: 
281: * [[Glenn Brunette>>http://blogs.sun.com/gbrunett]]
282: 
283: === Additional References
284: 
285: * [[Glenn Brunette’s Blog articles on the Solaris Package Companion>>http://blogs.sun.com/gbrunett/tags/tool-spc]]
286:
OpenSolaris

Top Menu

Wiki code for Solaris Package Companion

Search

Collectives

Community Group

Project

User Group

Subsites

Project svr4_packaging Pages
