Hi Johan,
Just reporting that everything works for me on Windows 8 with HP 2013.2.0.0 and the included GHC 7.6.3. I was able to build and install our three projects and all their dependencies (incl. lens, gitit, MissingH, glpk-hs...) from scratch (I removed Roaming/cabal and Roaming/ghc).
But it wasn't without problems.
With HaXml package: the latest version (1.24.1) no longer compiles with GHC 7.6.3. So when the build failed, I manually cabal installed HaXml-1.24, which worked, and then I could finish the build of my projects. It would be good if cabal somehow took into account the lowerbound of the compiler version required for a package, so that HaXml-1.24.1, for example, could say it requires ghc >= 7.8.2 and cabal would pick HaXml-1.24 which works with 7.6.3 instead. Of course, what I have to do now is to specify the upperbound on HaXml...
Also, sometimes I am getting messages similar to this (it was also hapenning with 1.18.*):
$ cabal install pandoc-1.11.1
Resolving dependencies...
Failed to install pandoc-1.11.1
Last 10 lines of the build log ( C:\Users\mantkiew\AppData\Roaming\cabal\logs\pandoc-1.11.1.log ):
cabal.exe: C:\Users\mantkiew\AppData\Roaming\cabal\logs\pandoc-1.11.1.log:
does not exist
The file "pandoc-1.11.1.log" indeed does not exist. After I manually create an empty log file, I get this:
$ cabal install pandoc-1.11.1
Resolving dependencies...
Failed to install pandoc-1.11.1
Last 10 lines of the build log ( C:\Users\mantkiew\AppData\Roaming\cabal\logs\pandoc-1.11.1.log ):
cabal.exe: Error: some packages failed to install:
pandoc-1.11.1 failed while unpacking the package. The exception was:
C:\Users\mantkiew\AppData\Local\Temp\pandoc-1.11.1-4732\pandoc-1.11.1\dist-tmp:
MoveFileEx
"C:\\Users\\mantkiew\\AppData\\Local\\Temp\\pandoc-1.11.1-4732\\pandoc-1.11.1\\dist-tmp"
"C:\\Users\\mantkiew\\AppData\\Local\\Temp\\pandoc-1.11.1-4732\\pandoc-1.11.1\\dist":
permission denied (Access is denied.)
the "pandoc-1.11.1-4732" does not even exit. Of course, on subsequent attempts, the number is changing after package version. Nothing I tried worked. The only way out of this is to completely remove the Roaming/cabal and Roaming/ghc folders and begin from scratch. Then it worked. I wasn't able to reproduce this behavior -- it seems random. Why would cabal report access denied for non-existing files/folders?
Finally,I love the speed (jobs: $ncpus) :-D
Thanks!
Michal