On 08/07/2018 02:15 AM, Evan Donahue wrote:
> Yes, that's right. As long as I don't "store settings" everything is
> ok, but if I do find myself wanting to change a global setting of some
> kind, and I hit "store," it /also/ stores the metacello paths, which
> will then be incorrect for the next
The settings that you save will apply to all images - so you need to clear out
those settings for shared repo’s etc.
I think what is confusing is that using the Save button - means apply the
settings to all images. If you change the setting locally in your image and
don’t press save, it
Hmm, the only things I'm trying to accomplish are 1) use Pharo Launcher and
2) have each new image keep its repositories separate, as advised by others
on the list, so that different images can check out different branches. Does
that set up require custom scripting to adjust the repo path?
The
Evan Donahue wrote
> Is there a way to handle settings that should be different for every
> image…
Startup script?
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Is there a way to handle settings that should be different for every image
when using Pharo Launcher?
In particular, Settings > Software Configuraiton > Monticello > Default
Local Repository & Local Cache Directory should be specific to the new
image, but if I ever store settings for any reason,
