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
stack path --global-stack-root reports the root. But as far as I can see this is hard coded? There is no analog of stack --local-bin-path or an environment variable like STACK_YAML to control the root?
My use case is to pick between machine-local and NFS installations of stack. That is, we may have ~/.stack necessarily as an NFS-stored directory, for machines where we don't have any local mounts. But then ones where we do, we could do something like the following
if [ -d /home.local/me/.stack ];thenexport STACK_GLOBAL_ROOT=/home.local/me/.stack
...
The text was updated successfully, but these errors were encountered:
The STACK_ROOT environment variable sets the location. That could definitely be documented better (it's only in the installation instructions). Not sure why the inconsistency between that name and the stack path --global-stack-root argument, might be nice to fix. And having it overridable on the command-line would be nice too.
stack path --global-stack-root
reports the root. But as far as I can see this is hard coded? There is no analog ofstack --local-bin-path
or an environment variable likeSTACK_YAML
to control the root?My use case is to pick between machine-local and NFS installations of stack. That is, we may have
~/.stack
necessarily as an NFS-stored directory, for machines where we don't have any local mounts. But then ones where we do, we could do something like the followingThe text was updated successfully, but these errors were encountered: