local-bin-path is not relative to the stack.yaml that specifies it

[rrnewton]

We like to have projects that build all the stack-built binaries into ./bin within the project directory so that other scripts can easily find them. But we were surprised to find that relative paths are interpreted relative to wherever stack runs, not the stack.yaml file containing the path.

Steps to reproduce:

With stack 0.1.6.0., put following line in stack.yaml:

local-bin-path: ./bin/

Switch to a subdirectory and build:

$ mkdir ./bin/
$ mkdir ./foo/
$ cd foo
$ stack build 
No directory could be located matching the supplied path: ./bin/

Expected behavior:

That ./bin is relative to the stack.yaml file that contains it.

Actual:

That local-bin-path is relative to the directory in which stack build is executed, which can be a deep subdirectory because of the automatic "look upwards to find stack.yaml" behavior.

[drwebb]

This seems very reasonable to me, and a pretty minimal change.
On Nov 12, 2015 7:22 AM, "Ryan Newton" [email protected] wrote:

We like to have projects that build all the stack-built binaries into
./bin within the project directory so that other scripts can easily find
them. But we were surprised to find that relative patths
Steps to reproduce:

With stack 0.1.6.0., put following line in stack.yaml:

local-bin-path: ./bin/

Switch to a subdirectory and build:

$ mkdir ./bin/
$ cd foo
$ stack build
No directory could be located matching the supplied path: ./bin/

Expected behavior:

That ./bin is relative to the stack.yaml file that contains it.
Actual:

That local-bin-path is relative to the directory in which stack build is
executed, which can be a deep subdirectory because of the automatic "look
upwards to find stack.yaml" behavior.

—
Reply to this email directly or view it on GitHub
#1340.

[drwebb]

@rrnewton: local-bin-path relative tot the project dir should be the behavior now with f8d0129