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
{{ message }}
This repository has been archived by the owner on Apr 25, 2020. It is now read-only.
Stack allows you to specify an alternate location for the stack.yaml file using the --stack-yaml command line option or the STACK_YAML environment variable. I don't like to clutter up the root directory of my repositories so I store my stack.yaml files in a build directory.
ghc-mod should allow you to specify an alternate location for the stack.yaml file using either a new command line option or by respecting the STACK_YAML environment variable.
It's actually recommended in the stack documentation to have multiple YAML files if you want to support multiple resolvers. This would be another motivation for supporting alternate stack configuration files in ghc-mod.
The text was updated successfully, but these errors were encountered:
The path isn't used anywhere we only use this to check for it's existence and invoke stack directly for everything else. So all you need to do is insert the appropriate logic there and it should work.
Stack allows you to specify an alternate location for the
stack.yaml
file using the--stack-yaml
command line option or theSTACK_YAML
environment variable. I don't like to clutter up the root directory of my repositories so I store mystack.yaml
files in abuild
directory.ghc-mod
should allow you to specify an alternate location for thestack.yaml
file using either a new command line option or by respecting theSTACK_YAML
environment variable.It's actually recommended in the stack documentation to have multiple YAML files if you want to support multiple resolvers. This would be another motivation for supporting alternate stack configuration files in
ghc-mod
.The text was updated successfully, but these errors were encountered: