[ bcc'ing install-discuss, copying pkg-discuss ] As you'll learn, scripting during an install is decidedly a no-no in the new world of IPS. Any arbitrary code that needs to run in order to complete the install must be done by a service which is either run when the image is next booted, or, if in a live image, after the install is complete, pkg(5) will restart one or more services at the packages' request.
Now, with that in mind, you have two options. One is for each package that wants to participate in this index to deliver one or more files in a special directory that your service will read and use to build the index. The second possibility is that you'll deliver your information as package attributes (pointing to URIs), and your service will simply gather all those attributes and rebuild the index as necessary. Which one you choose depends somewhat on whether you want to deliver actual data, or just things like URIs. I'll also note that we intend to deliver documentation in the same package that delivers the functionality. This will likely mostly be man pages for the core Solaris bits, but also whatever text and html documentation might come along with the various bits of opensource we ship. One thing you don't mention is exactly what this index is. Is it an html page sitting on the system? How do you expect that people will access this index? How do you expect they'll discover it? Danek
