On Mon, Jun 15, 2009 at 11:53:13PM +0100, Peter Tribble wrote: > > You can implement this w/ actuators in IPS; it will require > > a SMF service to be running to handle your post-installation > > tasks. Note that packages built this way will actually work > > on alternate root install, with Oracle running once that > > environment is booted. > > If that's the way to do it, and if it's possible to automatically convert > scripting into services, then why not fold that functionality into the > packaging system so that it creates the SMF services (or whatever) > as required to get the scripts run in the correct context?
I've posted a prototype. There's been little or no interest. I assume that means that manual pkg script migration is good enough for those doing that now, though that would mostly be engineers working on Solaris. Customers might have a different view (but see below). > It seems to me that the no scripting rule is more about the context in > which the script runs rather than the existence or content of the script. _Exactly_. > In that case, going to software packagers and saying "just write your > script to run correctly on a live image and we'll make sure its gets run > in the right time and place without you having to worry about all these > other possible installation scenarios" would be a big selling point. And > the packagers wouldn't have to worry about implementing the SMF > services, avoiding a big hole they could dig themselves into. I agree, but in practice developers will have to at least choose an SMF FMRI. That's because that way you get a handle that can be used to check self-assembly status (which my SVR4->IPS scripting tool does not give you, though it could, but at the cost of creating more interfaces and at the cost of not getting dependency evaluation in running of self-assembly). Nico -- _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
