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 new image I create. Also, even if > I delete them, it seems to autogenerate one (but not both) of the > paths incorrectly (with that crazy /build) path. > > More generally though, all I was trying to do was use Pharo launcher > and keep repositories separate, which I was advised to do by the list. Hi Evan, yes exactly. the default if i dont change & _store_ settings is: i make via launcher a pharo6.1blabla, it has its own repository-directory; i make the next one, pharo6.1blabla-01, open monticello and it has another package-cache. i did not test this, but i guess it could be possible that if you store settings just once even _without_ changing anything, the local cache directory will be stored, as the class-var-accessor produced a valid path, and from then on this setting will not change anymore for new builds via launcher.
you either reset the settings via deleting the monticello records in the settings file found via StartupPreferencesLoader preferencesVersionFolder. or if you need to store changed settings in a general way eg for all 6.1 versions, you do that deleting afterwards. i agree that the 2 monticello-settings behave differently and that this is either irritating or probably a bug (because the second behaviour can make storing other settings difficult), but then <shrugging shoulders> i have to admit i was never bothered by this behaviour. werner
