[Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

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

Re: [Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

On Wed, Aug 2, 2017 at 9:16 AM, Tim Mackinnon 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 f

Re: [Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

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

Re: [Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

Try to run the image with --no-default-preferences. -- Pavel 2017-08-02 14:37 GMT+02:00 Tim Mackinnon : > 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

Re: [Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

A that’s how it works… StartupPreferencesHandler and its in my user/Library/Preferences/Pharo/6.0 folder… You learn something new every day (minute it seems lately) Tim > On 2 Aug 2017, at 14:04, Pavel Krivanek wrote: > > Try to run the image with --no-default-preferences. > > -- Pavel >

Re: [Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

Mariano - out of curiosity, how do you build your image - do you use zero conf and then apply a known .st script? (I used to use pharo launcher back in the day - but now I find that zeroconf is actually handier anyway). Tim > On 2 Aug 2017, at 13:24, Mariano Martinez Peck

Re: [Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

On Wed, Aug 2, 2017 at 10:50 AM, Tim Mackinnon wrote: > Mariano - out of curiosity, how do you build your image - do you use zero > conf and then apply a known .st script? (I used to use pharo launcher back > in the day - but now I find that zeroconf is actually handier anyway). > > My work flow

Re: [Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

I’d be curious about your script if it is easily handy (I did notice a blog article you wrote on StartupLoader a while back). By the way - I really appreciated your article "Moving contexts and debuggers between images with Fuel” - it inspired me to figure it out for debugging on AWS lambda (wh

Re: [Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

On Wed, Aug 2, 2017 at 12:04 PM, Tim Mackinnon wrote: > I’d be curious about your script if it is easily handy > As said, nothing fancy at all [1]. And it keeps evolving all the time as Pharo evolves too. > (I did notice a blog article you wrote on StartupLoader a while back). > > Yeah, but t

Re: [Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

On Wed, Aug 2, 2017 at 2:37 PM, Tim Mackinnon 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 do