On Feb 11, 2004, at 1:01 AM, Marcus Denker wrote:

> Could we come up with a way to build the update stream automatically 
> for those packages?
>
> So we'd have updates.squeakfoundation.org, which get's notifed if 
> there's a new release
> on SqueakMap. Then the server build a delta (using mc) between the new 
> version and the
> release before that, and puts it out as an update automatically.
> (I don't now how versioning is handled in the image, but i'm sure that 
> delta-cs could do the
> right thing in the postscript).

Well, we certainly could do this, but it would be less robust than 
loading the packages with Monticello directly.  In the scheme you 
describe, what if between official updates someone loads a new version 
from the developer's repository?  Now the delta won't apply correctly.

I'm certainly willing to do it as a stopgap measure if people are 
squeamish about making the update stream directly depend on MC, but it 
feels like unnecessary effort.

> The updates-server would have a web-interface, with the possibility to 
> define your own update
> stream with your own set of packages. And it would have RSS support, 
> with nice reports about
> what gets added.

Is it so important that users not have MC loaded that we need old-style 
update streams even for individual packages?