<feed xmlns='http://www.w3.org/2005/Atom'>
<title>cabal-helper.git/tests/custom-setup, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://g.ypei.me/cabal-helper.git/atom?h=master</id>
<link rel='self' href='https://g.ypei.me/cabal-helper.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://g.ypei.me/cabal-helper.git/'/>
<updated>2020-05-02T13:44:26+00:00</updated>
<entry>
<title>Fix Cabal version selection for build-type:Custom</title>
<updated>2020-05-02T13:44:26+00:00</updated>
<author>
<name>Daniel Gröber</name>
<email>dxld@darkboxed.org</email>
</author>
<published>2020-01-11T06:46:33+00:00</published>
<link rel='alternate' type='text/html' href='https://g.ypei.me/cabal-helper.git/commit/?id=852dbc69d276e19add3917d17dff5541d84e29d4'/>
<id>urn:sha1:852dbc69d276e19add3917d17dff5541d84e29d4</id>
<content type='text'>
Previously we would pick up Stack's Cabal version with ghc-pkg on the
global package-db. This however ignores that Stack also supports custom
Setup.hs with the Cabal version from the snapshot instead.

In cabal v2-build we have a similar problem. We used to assume that
plan.json's cabal-lib-version is used uniformly across units but this is
similarly untrue.

To fix both of these we re-stage the cabal version query to after
reconfiguring a unit, then we can just lookup the Cabal version in
setup-config.

Fixes #95
</content>
</entry>
</feed>
