Danek Duvall wrote:
The rule of thumb is: if something is required for another action to successfully install, or is required for boot, then it's a candidate for an action. Otherwise, it's up to the application to figure out what to do at runtime, service start-up, etc.
The more the packaging system knows about Solaris internals, the more difficult it is to make upgrade work across a wide variety of releases. Any actions have to work across all the releases we support in order for upgrade to work; adding more config file syntax into the packaging system is something we'd like to avoid whenever possible. - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
