Supporting GHC 6.10 and 6.12 in HDBC-postgresql Setup.hs
Hi folks, I've gotten some reports (see below) of issues with building HDBC-postgresql on GHC 6.12. Its Setup.hs file [1] is the culprit. The problem is that AnyVersion needs to be removed to work with Cabal in GHC 6.12. But I still want to support older Cabal. Following the directions in the Cabal manual, I tried: #if MIN_VERSION_Cabal(1,8,0) pgconfigProgram (withPrograms lbi) #else pgconfigProgram AnyVersion (withPrograms lbi) #endif While of course adding the needed bits to invoke CPP. This didn't resolve it; apparently Cabal doesn't define macros for use in Setup.hs, only for use in the application. There also seems to be no conditional for use in the .cabal file to resolve this. I could check the GHC version, but that doesn't necessarily correspond to Cabal version. Any ideas? -- John [1] http://git.complete.org/hdbc-postgresql?a=blob;f=Setup.hs;h=0656cb41adc814de...
jgoerzen:
Hi folks,
I've gotten some reports (see below) of issues with building HDBC-postgresql on GHC 6.12. Its Setup.hs file [1] is the culprit. The problem is that AnyVersion needs to be removed to work with Cabal in GHC 6.12.
The other HDBC problem I have is various dependencies relying on QC1. The next HP will ship with QC 2.1 (in coming weeks), so it might be a good time for people to start migrating, since that will be the only version of QC on many distros. -- Don
The other HDBC problem I have is various dependencies relying on QC1.
The next HP will ship with QC 2.1 (in coming weeks), so it might be a good time for people to start migrating, since that will be the only version of QC on many distros.
I would strongly suggest moving to QC 2 for other reasons as well. It does substantially better at searching the random space, to the extent where several of my properties pass under QC 1 but fail under QC 2. It's a much better testing tool. Thanks, Neil
Neil Mitchell wrote:
The other HDBC problem I have is various dependencies relying on QC1.
The next HP will ship with QC 2.1 (in coming weeks), so it might be a good time for people to start migrating, since that will be the only version of QC on many distros.
I would strongly suggest moving to QC 2 for other reasons as well. It does substantially better at searching the random space, to the extent where several of my properties pass under QC 1 but fail under QC 2. It's a much better testing tool.
I will be making that change once it gets into haskell-platform (and once I have the time). My more urgent problem, though, is maintaining Cabal compatibility with 6.10 and 6.12. -- John
Thanks, Neil
participants (3)
-
Don Stewart -
John Goerzen -
Neil Mitchell