Peter Tribble wrote:
> But that problem arises not because SVR4 packaging supports scripting
> but because it only does so badly. What's needed is:
>
> 1. For the packaging system to fully support scripting as a first-class
> citizen. Which could include actually providing the most common
> functions as builtins.
>
> 2. For all scripts to be written assuming they're running in the live
> context, which is easy to do and the only place most script
> writers will bother to test.
>
> 3. For the packaging system to itself take on the responsibility of
> ensuring that scripts are run in the correct context.
>
> SVR4 fails here because it shirks the responsibility, passing it onto
> every script writer. But that wouldn't be terribly hard to fix.
>
> IPS ought to do this right, and is pretty much there because it actually
> does have the framework to do everything correctly, but claims that
> scripting is forbidden and therefore doesn't provide the public hooks,
> again forcing every script writer into carrying the responsibility themselves.
Actually that's pretty much what IPS does, it just leverages SMF as the
mechanism for ensuring that custom scripts are run in the correct context,
using actuators to start the SMF service immediately after package installation
or allowing SMF to start it on first boot if not installing to the live image.
The most common functions are builtin actions, like the one to install
a device driver.
So the biggest gap in IPS is the long acknowledged lack of documentation &
examples.
--
-Alan Coopersmith- alan.coopersm...@sun.com
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
