I'm still green WRT IPS and the various Sun repos. I think I know
enough to ask the proper questions, but since I've never actually done
anything except verify I can duplicate the examples in the IPS guide, I
need to test the validity of my understanding.
Background:
My goal is to get the SAM-QFS product into the IPS extra repository. In
SVR4 terms, this product has four packages; two main variants, each with
root and user.
The SAM-QFS product is a file system with an integrated HSM. Each SVR4
package has a number of scripts; the usual preinstall/postinstall and
preremove/postremove. In addition, there is a script that runs on
initial install that is interactive; one part handles a mandatory
license acceptance, the other handles initial defaults. I can modify our
product such that mounting or any SAM-QFS command execution can trigger
the interactive script under the proper conditions.
There are two SMF services defined by this product. Their main purpose
is to control daemons associated with the file system. Note that the
various files delivered by this product cannot just be updated or
removed. There can be no mounted QFS file systems, HSM processes, etc. .
We cannot control this via SMF alone. All we can do under SMF is fail
the disable and log the fact that there are mounted file systems.
How to run the scripts associated with SVR4 package operations (please
verify):
One design pattern I found uses IPS's ability to create and control SMF
services to run the non-interactive scripts. Is this a valid approach?
I assume the service is enabled after the all directories and files are
installed.
I also assume that the service is disabled before any updates or removals.
How does an IPS image update interact with these SMF services?
If I combine an SVR4 root and user package in a single IPS package,
should I use two services; one for user and one for root?
How do I specify the association between an SVR4 package and SMF
service, if I have multiple SVR4 packages in one IPS package?
Is it kosher to create two IPS packages (one for root and one for user)
and then make the user dependent on root?
Package dependencies questions:
I believe the normal practice is to combine root and user SVR4 packages
into one IPS package. Do the tools (pkgsend for example) assume that
user is dependent on root, or does this need to be explicitly declared?
How an SVR4 package gets into the extra repo (please verify)
I believe that the mechanism by which an SVR4 package gets published
into the extra repo is via the extra gate. I believe that each machine
architecture (or common if it doesn't matter) that the SVR4 package
supports needs a file in the appropriate directory that essentially
defines the importation of the SVR4 package.
In the context of the previous questions, if I want to define
dependencies outside the automated importation, how doe I do this?
Ditto for services.
Thanks for your help.
--- Todd
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
