Closed evertedsphere closed 3 years ago
Not a cabal-install
bug, this is just a consequence of the fact that this library isn't generally useful without the specific fork of resource-pool
that is used here.
The cabal.project
file in this repo only provides dependency overrides for local builds.
When a library or application depends upon pg-client-hs
, cabal-install
will first try to resolve a compatible version of resource-pool
by looking at whatever package set it has available (e.g. Hackage).
In other words, if you were to try to build this project with stack
you'd have to add the appropriate resource-pool
source to the extra-deps
stanza in stack.yaml
.
Without this stack
would try to look for the version of resource-pool
in its package set, which would fail to build with the same error you're seeing here.
ah, yeah, my model of how cabal resolves dependencies seems to have been somewhat nix-like lol
seems like a cabal bug, but for posterity:
on a project depending upon
92975d0f8f933c8d06913dc97af259253bf7fb5f
(currentmaster
HEAD
, as well as the version used bygraphql-engine
currently), i get errors likeit seems i have to manually add the
source-repository-package
block forresource-pool
to thecabal.project
file, with the exact same contents as the corresponding block in this project'scabal.project
file.