On Thu, Mar 25, 2010 at 9:27 AM, Stéphane Ducasse <stephane.ducasse@inria.fr
wrote:
save as doe not work? because I do simply save as.
Yes, it works. But you have to do, system about, copy the version, and then put it in the save us popup hhahaa there are persons VERY lazy :)
On Mar 25, 2010, at 3:51 AM, Hernán Morales Durand wrote:
Hi, I've noticed every time I update a Pharo image I should rename manually the image and changes file names to match the new updated version number. I.e.:
If you have PharoCore-1.1-11291-UNSTABLE.changes PharoCore-1.1-11291-UNSTABLE.image
then update to #11295 and save and quit, you should modify the file names manually to
PharoCore-1.1-11295-UNSTABLE.changes PharoCore-1.1-11295-UNSTABLE.image
The attached files does the following:
-After a Pharo software update, evaluate the FileOutNewNamesAfterUpdate.st script -Quit the image -For Win users: Run the batch updateFileNames.bat to rename the image and changes files to the latest version. (this is not the same as Save as...)
Feel free to modify and use it as you want :) Cheers,
Hernán
<FileOutNewNamesAfterUpdate.st><updateFileNames>_______________________________________________
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project