Darren J Moffat wrote: > covered as an IPS action. I did say that I wasn't claiming that IPS didn't cover these things, that I was enumerating uses that I'd seen preinstall put to.
>> - 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. SUNWckr, SUNWdhcsr, SUNWhalr, SUNWldomr.v, SUNWntpr, SUNWpoolr, SUNWpsr... just look through usr/src/pkgdefs/*/preinstall in ON; it's probably about a third of them. I suspect that this pattern is misguided, that there are much better ways to accomplish its goals, but I haven't investigated in detail. >> - 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. Yes, but that's normally (and probably more correctly) done with postinstall, and we were discussing preinstall here. _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
