Post-release retro-compatibility liberation, yay!
Following this mail thread [1], here is a patch that requires GHC 8.2
and Cabal 2.2. Some changes are weird (Putting the cabal version as the
first line of darcs.cabal) but they are required by the library. See
https://hackage.haskell.org/package/Cabal-2.2.0.1/changelog for more
information. Cabal developers say a 3.0 version is planned for mid-2018
so it does not seem too strict to me to require Cabal 2.2 instead of 2.0.
The second patch reverts a dependency changes on directory that we had
to do before the 2.14 release.
2 patches for repository http://darcs.net:
patch 2a6acf4563bec0f3df8ddaa95528987bc2168639
Author: Guillaume Hoffmann <guillaumh@gmail.com>
Date: Fri Apr 6 16:17:09 -03 2018
* require directory 1.2.7 and use doesPathExist
patch 887c67e5d7a901ab3a93d29ab17f8d91b7faa456
Author: Guillaume Hoffmann <guillaumh@gmail.com>
Date: Fri Apr 6 16:18:27 -03 2018
* require GHC 8.2 and Cabal 2.2
[1] https://lists.osuosl.org/pipermail/darcs-devel/2018-March/018663.html
I support moving forward with this - I think it's relatively likely
we'll discover issues with being on the Cabal bleeding edge as we try
to use it in anger, but we can always roll back some or all of the
changes as we run into problems.