On Fri, May 09, 2008 at 04:58:22PM +0100, John Levon wrote: > What's the plan for adding actions?
To add as few as possible. Actions should generally only be needed to deliver objects to the filesystem and their metadata, as well as anything that needs to be done for the system to boot. The former group consists of files, users, groups, etc, and the latter of things like driver actions. > For example, it looks like pkg needs a syseventadm action. So the discussion in bug 509 indicates that this isn't actually needed for boot, but could be done via an SMF service that runs at boot. Is that not the case? > Presuming this can be delivered in an update, how would I deliver > packages that depend on that action to exist? Would I just depend on a > certain version of the pkg package, or what? I don't think we've settled on a mechanism for this yet, but I think we're leaning towards making this as automatic as possible -- either the IPS package is always updated automatically, or all manifests are scanned for unknown actions (and IPS-specific, but unknown, attributes), and upgraded (or a warning given) if any exist. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
