On Thu, Sep 13, 2007 at 09:52:48AM +0200, Casper.Dik at sun.com wrote: > Or properly define and limit "scripting".
Well, the system does (or can do) more than *just* lay down bits. Its just that a package isn't given an opportunity to deliver its own arbitrary code to do that. When it delivers an object, that object may be more specific than "file" or "directory". It may be "user" or "service" or "driver". The code that's part of the packaging system will then do extra things with it, like run useradd, svcmumble, or update_drv, based on the properties of the delivered object. The set of these "actions" and their specific behaviors can be changed, but the code is maintained by the packaging system. They're much like class action scripts, except you can't deliver your own. The set of recognized actions will obviously need to grow over time (at first, certainly). A customer may need to upgrade the packaging system before being able to perform some installs, much like live upgrade today needs to be upgraded before anything else. There's room for the ability to do that automatically. However, not all things currently requiring scripting are candidates for actions; there will likely be an increase of operations that are performed on the system once it's running natively. Danek
