Joseph Di Pol wrote:
I understand the concern that arbitrariness implies lack of safety. But relying on the creation of new actions (or action behaviors) for things we can't predict implies lack of agility and flexibility. And I would claim that this will have more of a negative impact on users than the potential risks posed by UserImageActuators.
If you leave the design of actuators to a per-package engineering effort, you're back at scripts, one for each package, one for each architecture. This is insane. Your group needs to deliver and own packages that deliver the needed user services on the various platforms on which you deliver. You also need to figure out how to make this work if the platform isn't running when the image is created. "Well, we'll just script that when we run into problems" is not the right way to deal with this. - 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
