Hi,
user-level automatic software updating [...] where
significant customizations only occur in the
package/package-key/www and siteroot/www sections
The Project/Open case is relatively simple, because users probably won't modify much of the code. That's possible because the P/O "core" architecture has a lot of flexibility built-in, such as dynamic views and the option to aggregate data to an existing object.
Our main focus is to distribute small bug-fixes.
not the piece of cake as it might sound
Right. I see that this is definitely not going to be a solution for generic OpenACS software updates. Maybe the "Arch" version management system is the better solution if you have heavy customization?
I'm still unsure...
Thanks for the feedback,
Frank
