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
