This is optional (some people want it, others not) System settings > Monticello > Local cache directory
MCCacheDirectory class>>#cacheDirectory: > On 24 Jun 2016, at 15:54, Javier Pimás <[email protected]> wrote: > > I don't know for the new directories, but I always thought that it would be > nice to have package-cache in ~/.pharo or a place shared by all images, to > avoid redownloading all .MCZs from other projects each time you launch pharo > from a different directory. > > Cheers! > Pocho > > On Thu, Jun 23, 2016 at 12:22 PM, Esteban Lorenzano <[email protected]> > wrote: > Hi, > > Since some time I’ve seen growing the amount of files/directories generated > when running Pharo. Up to Pharo 2.0, we had just this: > > Pharo.image > Pharo.changes > PharoDebug.log > pharo-cache > > now we have: > > Pharo.image > Pharo.changes > PharoDebug.log > pharo-cache > epicea-sessions > play-cache > play-stash > > it does not looks like much, but I think this does not looks professional (we > take too much from user space). So I proposed (and implemented) a > “concentrator” directory: > > Pharo.image > Pharo.changes > ./pharo > … and everything for “pharo working internally” here > > then users have again control about what they have along with the image (this > allows to some nice strategies too, when we want a version that does not > pollutes the file dir). > > of course, this idea follows other developing spaces, where things are stored > in same fashion way… for example in eclipse for java they store all eclipse > data under .workspace directory. > > so, please note that this is NOT user space… regular pharo users will store > his files along with the image, for instance filetree repositories… something > like: > > Pharo.image > Pharo.changes > .pharo/ > voyage/ > punqlite/ > etc. > > well… I will commit a SLICE with the changes soon (is not a hard change at > all). > > But then: > > is ./pharo a good name? > will this work? > > Esteban > > > > -- > Javier Pimás > Ciudad de Buenos Aires
