On Fri, Jun 24, 2016 at 12:49 AM, Cyril Ferlicot D. < [email protected]> wrote:
> Le 23/06/2016 à 17:22, Esteban Lorenzano a écrit : > > 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? > > > > +10000 for the reordering :) > > `pharo` is maybe a little too common. Agreed. > What about `pharo-local`? > Or pharodata... cheers -ben
