Fix build with persistent-2.10.

Added an additional constraint that persistent needs.
This also builds with persistent-2.9.2 without needing any cpp.
This commit is contained in:
Joey Hess 2019-10-17 11:58:31 -04:00
parent d0d416b215
commit 904b175707
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 43 additions and 6 deletions

View file

@ -71,3 +71,5 @@ The Glorious Glasgow Haskell Compilation System, version 8.6.5
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
git-annex has been awesome for managing a massive collection of raw images and video clips across several storage targets and editing systems.
> [[fixed|done]] --[[Joey]]

View file

@ -0,0 +1,26 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2019-10-17T15:04:29Z"
content="""
Thank you for maintaining the homebrew build, and for tracking down the
persistent version.
I've fixed this now, and will be making a new git-annex release today.
FWIW, git-annex.cabal intentionally doesn't pin higher bounds of library
versions. My thinking is that people who want a build pinned at known
working versions should use stack to build, while people who are building
with cabal tend to be the kind of people who are integrating git-annex with
a larger system, and will probably want to build with whatever library
versions shipped with their system (eg in a linux distribution), or
with the latest and greatest.
That does mean that everyone building with cabal is likely to run into this
kind of breakage now and then, rather than me not noticing it until I update
the pinned versions. Kind of offloading a bit of the work from me onto users,
I have to admit.
You can of course patch git-annex.cabal to use an older version if
necessary.
"""]]