Using cabal with --allow-newer will break the build as of directory 1.3.8.2. The problem is that the os-string flag introduced in #165 defaults to the older way, so it will end up not using os-string even though it will be on the latest version of filepath. For now, I'm working around this by also passing -c 'directory +os-string' to cabal, but that shouldn't be necessary for everyone who ever uses --allow-newer. Any one of these three changes will fix it:
- Changing that flag to
default: True
- Keep the flag
default: False, but invert the meaning of it, like QuickCheck does
- Get rid of the flag altogether, and use
os-string on GHC 9.2+ instead, like Hashable does
Using cabal with
--allow-newerwill break the build as of directory 1.3.8.2. The problem is that theos-stringflag introduced in #165 defaults to the older way, so it will end up not using os-string even though it will be on the latest version of filepath. For now, I'm working around this by also passing-c 'directory +os-string'to cabal, but that shouldn't be necessary for everyone who ever uses--allow-newer. Any one of these three changes will fix it:default: Truedefault: False, but invert the meaning of it, like QuickCheck doesos-stringon GHC 9.2+ instead, like Hashable does