Hi, Danek Duvall p????e v ??t 13. 09. 2007 v 07:35 -0700:
> 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. > And what if this new "action" will be needed by some third-party package? Will it be "pluggable"? Or just "OSol" will be the right and only possible source of "actions"? Best regards, Milan P.S.: Please, don't use word "customer", "user" is much better in this area.
