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 persists just in that image (is you can try something out). If you want most images to share a setting and just a few to not do it - then you would save the main setting - and just adjust locally when needed - or could have some startup script that recognised certain image names and applied something programmatically. Tim > On 7 Aug 2018, at 02:03, Evan Donahue <[email protected]> wrote: > > 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 cache path does seem to do the required adjusting on its own, but the > 'metacello default directory' path defaults to that crazy thing that's not a > path on my computer: > > /builds/workspace/Pharo-6.0-Update-Step-1-Tracker > > PS, Is the 'store settings' button in the settings menu the standard way to > configure cross-image preferences, because that seems to also save things > like these paths that should be generated anew with each new image. Maybe I > should stick with one single place for repos and just configure these paths > to be global? > > Thanks > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >
