Jordan Brown wrote: > I'm not sure of the relationship to user interaction, but there are > other important differences. Checkinstall is run as an unprivileged > user; all it *can* do is to collect data and perhaps veto the > installation. Preinstall, on the other hand, is run with full > privileges. It is expected to modify the system. Uses include: > - adding users before installing files owned by those > users.
covered as an IPS action. > - preserving files before upgrades (which would be better > done using class action scripts). covered as an IPS action. > - shutting down services prior to upgrading them. I'm assuming the manifest action covers this but in the 'image-update' case it doesn't matter because it can't be running since IPS isn't touching the live system. > - recording the installed/uninstalled state of the package > before installation, for use in deciding whether to > enable a service after installation. (This is remarkably > common in ON packages, and probably merits special attention.) Could could give an example of this. I think I know what you are saying but it isn't quite clear. > - cleaning up system state before an upgrade - e.g., removing > obsolete entries in configuration files. Or adding new ones! This is the bit that causes people to need to redesign stuff. It is this case that I need to address to replace the i.kcfconfbase and i.pkcs11confbase CAS scripts otherwise ZFS crypto won't work default on an IPS system. In our case we have actually worked out we don't need the config files at all anymore - but not everyone will be so lucky. -- Darren J Moffat _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
