Can somebody explain me what benefit we gain by using ScriptLoader for updates? What can it do more/better than just plain changesets?
Plain cs are used to load scriptloader version. The idea is that we can gather some logic in a class and metadata for some of the actions performed. Normally scriptloader should not stay in a final image. Then scriptloader is versionned in squeaksource, we want to avoid to have cs around.
Please have a look at
http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-June/129234.html
How we like to deal with?
In the past we prefered not to remove updates to have the complete history without having to reload each individual release script. Now I should clean a bit this class. Stef
Norbert
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project