jajajaj thanks Hern�n. You were less lazy than me. I always do the same (manually) ;)<br><br>Thanks!<br><br>Mariano<br><br><div class="gmail_quote">2010/3/25 Hern�n Morales Durand <span dir="ltr">&lt;<a href="mailto:hernan.morales@gmail.com">hernan.morales@gmail.com</a>&gt;</span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi, I&#39;ve noticed every time I update a Pharo image I should rename<br>
manually the image and changes file names to match the new updated<br>
version number. I.e.:<br>
<br>
If you have<br>
PharoCore-1.1-11291-UNSTABLE.changes<br>
PharoCore-1.1-11291-UNSTABLE.image<br>
<br>
then update to #11295 and save and quit, you should modify the file<br>
names manually to<br>
<br>
PharoCore-1.1-11295-UNSTABLE.changes<br>
PharoCore-1.1-11295-UNSTABLE.image<br>
<br>
The attached files does the following:<br>
<br>
-After a Pharo software update, evaluate the<br>
FileOutNewNamesAfterUpdate.st script<br>
-Quit the image<br>
-For Win users: Run the batch updateFileNames.bat to rename the image<br>
and changes files to the latest version.<br>
(this is not the same as Save as...)<br>
<br>
Feel free to modify and use it as you want :)<br>
Cheers,<br>
<font color="#888888"><br>
Hern�n<br>
</font><br>_______________________________________________<br>
Pharo-project mailing list<br>
<a href="mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project@lists.gforge.inria.fr</a><br>
<a href="http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project" target="_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project</a><br></blockquote></div><br>