Unintuitive semantics for imported project from a different folder

[hellwolf]

To illustrate what the title means, here is an example: when A/cabal.project imports A/B/cabal.project, I observe that inside the A/B/cabal.project packages, the package path is based on A, instead of more intuitively A/B.

An live example is here which has an import: import: 3rd-parties/cabal.project.

Cabal version 3.14

[ulysses4ever]

What cabal version are you using? Could you try cabal-head (the GitHub pre release has binaries)? We recently had an overhaul of path-related stuff.

[hellwolf]

Oh, I forgot to mention.

Cabal version 3.14

I will try a newer version at some point and report back.

[geekosaur]

I believe this is the current behavior, the old behavior was relative to the directory cabal was run in, and the correct behavior is relative to the file doing the import (compare #include in CPP, for example).