(Resending from a machine that's externally MX-able. Sigh. Sorry to the direct recipients for the dups.)
Darren J Moffat writes: > Liane Praza wrote: > > JDS's postrun is a similar idea, but gloms it all into a single service > > rather than allowing expensive or long-running actions to be parallelized. > > Isn't that just an implementation detail though rather than something in > the postrun design ? Possibly, but I don't know the full set of design constraints. (I believe Stephen and Dermot chatted about this on another alias, but could be misremembering.) Regardless, as a general-purpose solution, if we want to do parallelization, we probably need to allow capabilities for ordered actions across multiple packages/capabilities, as well as allow room in the design for potential throttling of simultaneous actions. So, you're probably solving dependencies already, which means that separate services are probably appealing. They're not the only solution, but I'm not currently aware that postrun is designed to solve the more general problem. I'm honestly not trying to design this on-alias, though. The previous enumeration of package add/upgrade scenarios that I tried to do in the 'upgrade' method thread was daunting. :) liane -- Liane Praza, Solaris Kernel Development liane.praza at sun.com - http://blogs.sun.com/lianep
