Smalltalk › Pharo › Pharo Smalltalk Developers

Auto-rename image and changes file after updating

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

hernanmd

Auto-rename image and changes file after updating

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

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

FileOutNewNamesAfterUpdate.st (1K) Download Attachment

updateFileNames (574 bytes) Download Attachment

Mariano Martinez Peck

Re: Auto-rename image and changes file after updating

jajajaj thanks Hernán. You were less lazy than me. I always do the same (manually) ;)

Thanks!

Mariano

2010/3/25 Hernán Morales Durand <[hidden email]>

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

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Stéphane Ducasse

Re: Auto-rename image and changes file after updating

In reply to this post by hernanmd

save as doe not work?
because I do simply save as.

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
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Mariano Martinez Peck

Re: Auto-rename image and changes file after updating

On Thu, Mar 25, 2010 at 9:27 AM, Stéphane Ducasse <[hidden email]> 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
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

hernanmd

Re: Auto-rename image and changes file after updating

But the Save as... doesn't rename the image and changes file, just
creates two files with the updated version number. With a simple batch
file you may send keystrokes to Pharo too and do some automated
building of images daily.
Cheers,

Hernán

2010/3/25 Mariano Martinez Peck <[hidden email]>:

>
>
> On Thu, Mar 25, 2010 at 9:27 AM, Stéphane Ducasse
> <[hidden email]> 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
>> > [hidden email]
>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project