You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the README file, the scale-bootstrap wrapper script is invoked from the project root, like so:
sudo ./build/scale-bootstrap ./build/install.st
That wrapper then runs the the install script like so:
./cache/pharo cache/Pharo.image scale "../$@"
From the point of view of build/scale-bootstrap, $PWD is the project root, and since it passes .././build/install.st to scale, that should resolve to a build directory one level up, besides the project directory. If the code in the image relies on FileLocator imageDirectory, then OK, but I'd change that to FileLocator workingDirectory, which should be equal to $PWD.
More a FileSystem than a Scale bug, but a nice illustration of it.
The text was updated successfully, but these errors were encountered:
cdlm
changed the title
scale-bootstrap illustrate the problem with workingDirectory…
scale-bootstrap illustrates the problem with workingDirectory…
Nov 4, 2016
As per the README file, the
scale-bootstrap
wrapper script is invoked from the project root, like so:That wrapper then runs the the install script like so:
./cache/pharo cache/Pharo.image scale "../$@"
From the point of view of
build/scale-bootstrap
,$PWD
is the project root, and since it passes.././build/install.st
to scale, that should resolve to abuild
directory one level up, besides the project directory. If the code in the image relies onFileLocator imageDirectory
, then OK, but I'd change that toFileLocator workingDirectory
, which should be equal to$PWD
.More a FileSystem than a Scale bug, but a nice illustration of it.
The text was updated successfully, but these errors were encountered: