On Wed, Aug 2, 2017 at 2:37 PM, Tim Mackinnon <tim@testit.works> wrote:

Hey thanks - that seems like a good strategy (I hadn��t though of sharing the GT ones as well).

However, I��m still curious how/why a new image would pick up settings from what I did in another image (at least I think thats what its done - certainly the directory it shows in my fresh image is not File @pharo-local/package-cache like I would expect it to be?

With regards to the GT settings - how does it work if you share them - do they happily co-exist?

They should co-exits with no issues if you share the play-cash and play-stash folders between multiple images.

��

The stash one is also quite new to me - Sven mentioned it a few weeks ago as I was confused how the playground got saved (I��m still not clear) - but he suggested double-clicking the title and giving the tab a name. Are these named ones the stashed ones (it looks like it). And do stashed ones honour cmd-s to save them? Which then leads to the question, that in different images - if you share the stash then I guess if you want to reload a file, you close that playground and then pick it again from the list?

The play-stash is for scripts you explicitly give a name.��You can double click on the tab and enter a name. Then a file with that name plus a timestamp is created in the play-stash folder. The content gets then saved to that file. Right now you can access the stashed scripts again though spotter by searching for the script name or typing #play to get the cached and stashed pages.

Cheers,

Andrei

��

Its quite a cool way of working (not perfect) but a real time saver. Thanks for sharing.

Tim
On 2 Aug 2017, at 13:24, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Wed, Aug 2, 2017 at 9:16 AM, Tim Mackinnon <tim@testit.works> wrote:
Hi - I��ve noticed that when I download a new image+vm with zeroconf (in a fresh directory) - that when I launch it, the setting Tools | Software Config Mgnmnt | Monticello | Local Cache Directory has a value that points to a directory from one of my earlier images.

Is this normal (does it store this information somewhere on my computer so that different setups can access it)?

At first I thought this was annoying - but I��m now wondering if this is useful as I��m guessing that there isn��t any reason to have separate caches for version controlled libraries and so maybe I should actually set it to some common directory?

What is the recommended strategy?

My strategy is to use a shared repository for all my images. As part of my build image scripts I do something like this:
" =============== Personal Settings ================ "

MCCacheRepository cacheDirectory: '/Users/mariano/Pharo/localRepo/' asFileReference.
MCGitHubRepository cacheDirectory: '/Users/mariano/Pharo/localRepo/' asFileReference.
GTPlayBook cacheDirectory: '/Users/mariano/Pharo/play-cache/' asFileReference.��
GTPlayBook stashDirectory: '/Users/mariano/Pharo/play-stash/' asFileReference.��
I guess you save stuff:

find /Users/mariano/Pharo/localRepo/ -type f | wc -l ��
�� 32301

��du -sh /Users/mariano/Pharo/localRepo
6.1G �� /Users/mariano/Pharo/localRepo

Not only you save disk space, but also:
1) Each image build is likely to take less time as many files will be already in the cache (no need to redownload it).
2) it works as a yet another backup of your code and other packages.��

--
Mariano
http://marianopeck.wordpress.com