* Bill Weir <[EMAIL PROTECTED]> [2008-08-05 10:16]: > Given the absence, as far as I am aware, of IPS scripts to execute > similar functions to the pkgadd request and preinstall scripts, does > anyone have any hints on how to migrate an SVR4 package that does the > following at preinstall time? Most of your package's aspects are built in today, or planned.
> - prompt for desired installation directory No prompts--this question isn't good even in an SVR4 package. Use user images to place package at any location. > - check for a couple of prerequisite user accounts: abort install if > they are not found Use user action to install user accounts; fails if privileges are insufficient or accounts don't exist. > - check for an existing installation of the same package: > -- abort install if existing version is newer, else: Automatically satisfied by package version numbering. > -- call the existing package's "stop" operation to stop its running > services We don't have support for smf(5) service suspension yet, but we will. > -- backup some files in the existing package, to prevent them being > overwritten by the new package Use the preserve attribute on your file actions. > There are a few more, but that should be enough to show what I'm trying > to achieve. I don't have a problem with migrating SVR4 *postinstall* > scripts, since I can put that stuff in a script to be run manually after > installation. However, I just don't understand how the sort of > *preinstall* things I listed above can be done in IPS. Surely some IPS > packages must do something similar? How do they do it? Please feel free to describe the other behaviours; we'd be happy to look at the postinstall as well--much of it can probably be absorbed into actions or action attributes. - Stephen -- [EMAIL PROTECTED] http://blogs.sun.com/sch/ _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
