Unnamed repository; edit this file 'description' to name the repository. https://g.ypei.me/cabal-helper.git/atom?h=master 2021-02-13T23:52:09+00:00 2021-02-13T23:52:09+00:00 Daniel Gröber dxld@darkboxed.org 2021-02-12T03:23:02+00:00 urn:sha1:0e9df088226d80669dd0882ed743bca871dce61c 2021-02-13T23:52:09+00:00 Daniel Gröber dxld@darkboxed.org 2021-02-12T03:22:50+00:00 urn:sha1:1fc6c10843d918efc921683aa66224561c5563f7 2020-05-20T07:53:08+00:00 jneira atreyu.bbb@gmail.com 2020-05-09T14:04:26+00:00 urn:sha1:cbd080a3a6107ec02e2129127d0676291cab19c6 2020-05-20T07:53:08+00:00 jneira atreyu.bbb@gmail.com 2020-05-08T20:23:05+00:00 urn:sha1:c4bfdcedc4620d2dfceb57925d9ced35544cf682 2020-05-10T19:50:44+00:00 Daniel Gröber dxld@darkboxed.org 2019-08-06T17:39:23+00:00 urn:sha1:bda559bf059ee42e3e01c1280f7a64dd2673d725 This mainly renames the program version getters to get* and make them consistenly return Version directly. Such that wrappers like GhcVersion have to be added at the callsites of the relevant functions. 2020-05-02T13:44:26+00:00 Daniel Gröber dxld@darkboxed.org 2020-05-01T21:13:48+00:00 urn:sha1:5b85a4b9e1c6463c94ffa595893ad02c9a3d2ec3 2020-05-02T13:44:26+00:00 Daniel Gröber dxld@darkboxed.org 2020-01-11T06:46:33+00:00 urn:sha1:852dbc69d276e19add3917d17dff5541d84e29d4 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 2020-05-02T13:44:26+00:00 Daniel Gröber dxld@darkboxed.org 2020-05-01T21:00:21+00:00 urn:sha1:11a515ed0e887eef081e514b51f29589cf6693ca 2020-05-02T13:30:11+00:00 Daniel Gröber dxld@darkboxed.org 2020-05-02T00:24:34+00:00 urn:sha1:15d23d0731aa4e592e709e3626444e18ce3f804a Stackage can get into the situation where they have a different Cabal version from what was shipped with GHC. This is usually not a problem but when stack installs any package with build-type:custom this pulls in the Stackage Cabal version! 2020-05-02T01:15:31+00:00 Daniel Gröber dxld@darkboxed.org 2020-03-25T17:40:15+00:00 urn:sha1:262231a8f28feb711a8b164c62d9b89bcc11df47 Apparently we can get source-repo-packages in plan.json even when filtering for `"style": "local"`(`UnitTypeLocal`). It's possible the root cause here is a cabal bug as source-repository-package should really be treated more like a tarball than a local package. Regardless we simply filter units by actually checking for `uPkgSrc=Just LocalUnpackedPackage` instead of relying on "style". This fixes #99