Replies inline.
Danek Duvall wrote:
> [ 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.
Thanks for that clarification.
>
> 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.
Well, we would most likely want to provide short descriptions for each
entry and associated metadata to help organize the index. So, I think the
first option would be better.
>
> 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.
So, for man pages, this integration is already established. But, how do you
plan to install the text and html documentation...will the information be
installed in a common location? Will there be a way to easily find all the
documentation installed on a Solaris system? What about information that
is provided outside of a package...like a wiki? That's what my proposal is
trying to address.
Is this new documentation delivery feature documented somewhere?
>
> 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?
My assumption is that it would be an XML file that could be used to
deliver the information in whatever format we choose. It could be available
as a link on the desktop or main link as part of the package install output.
There are a number of ways to get the word out...that will be the easy part. ;)
Thanks for all your feedback. Beyond your feedback, what do you think
of the overall need of my proposal?
Paul
>
> Danek
--
Paul Kasper | Information Lead | [EMAIL PROTECTED] | x51546
OpenSolaris Storage Community
http://opensolaris.org/os/community/storage
Storage Administration Wiki
http://wikis.sun.com/display/StorageAdmin/Home
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
