Tony Nguyen writes: > > What if the upgrade method wants to change dependencies? > > > > I think the upgrade method timing should be different than the start > > method timing. > > > > Perhaps the upgrade method should run twice: once early on in boot > > (where manifests are imported) and once right before the service is to > > be started. Obviously the method arguments/environment should > > distinguish between the two. > > > > > I think the new dependencies should probably be defined in the update > manifest.
Yes. Dependencies delivered by the manifest should be modified in the manifest. As David mentioned, moving manifest-import to the first thing during boot would alleviate any concerns about services starting before we've had the chance to change dependencies. For an update on a running system, you'd need to expect that your service is already running anyways. > Manifest-import reads the manifest, upgrade method executes > then followed by the start method. (Manifest import *or* the i.manifest class action script...) liane -- Liane Praza, Solaris Kernel Development liane.praza at sun.com - http://blogs.sun.com/lianep
