Yes you are right, each update should come with the latest version
of ScriptLoader. Usually this is how we do it. In update 10050 the
version loaded is ScriptLoader-al.468. The newer versions that are
in the Pharo repository were probably committed after we did the
update (?)
The last version of ScriptLoader is ScriptLoader-AlexandreBergel.
471.mcz, and the last Pharo image is Pharo0.1-10050-2008-07-19.
But at the time the image was released, the version ScriptLoader-
AlexandreBergel.470 was available.
Talking about the *released image* that we provide for download, I
think this one should be identical to the one that you can produce
from going through all updates of the stream. So, I would not
manually load newer versions of ScriptLoader afterwards. This is to
make sure that everybody has the exact same code.
Exact,
Alexandre
On Jul 29, 2008, at 11:12 , Alexandre Bergel wrote:
The last release does not have the last version of ScriptLoader
loaded.
I think it is good to have always the last version of
"infrastructural" packages in the image, like ScriptLoader.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
