Hi Stefan,
Le 8 nov. 2017 à 15:56, stephan <stephan@stack.nl> a écrit :
I run into all kinds of issues with the directory structure used by the new PharoLauncher. pharo-local seems to be shared now for multiple images.
I never saw this issue. PharoLauncher does not have influence on the pharo-local directory of launched images. pharo-local directory is located in the same directory as the image run. in a Pharo 6.1 image: localDirectory ^ self class userLocalDirectory ifNil: [ (self imageDirectory / self class defaultLocalDirectoryName) ensureCreateDirectory ] userLocalDirectory ^ UserLocalDirectory ifNil: [ FileLocator workingDirectory / self defaultLocalDirectoryName ] Maybe you run Pharo 7 images and this change « Build #203: 05723-Default-Working-Directory » has a side effect?
That makes using configurations practically impossible as they are not expecting to have to deal with pre-downloaded older and newer monticello files. The missing sources files is less of a problem.
Stephan