upgrading methods

>
> The latest versions of these packages should work. In case you run
> into some problems just ask again, I've done this a 100 times already
> ;-)

So this proves that may be we should have a way to say update to a  
package :")
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

This gives me the impression that it would be really important to  
have a protocol
to make sure that package developer can specify what action should be  
done on upgrade.
Doing all the time the same is a clear sign that we are missing  
something.


Stef
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

stephane ducasse wrote:
> This gives me the impression that it would be really important to have a
> protocol
> to make sure that package developer can specify what action should be
> done on upgrade.
> Doing all the time the same is a clear sign that we are missing something.

YES! Nail on the Head.
Especially since the recipe for updating will most likely change.

--
brad fuller
  http://www.Sonaural.com/
  +1 (408) 799-6124


_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Universes or something similar - up.     Hand written upgrade scripts -
down.


Brad Fuller wrote:

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside