This commit breaks the path module on Windows. This reverts commit df6fe40.
network-22.214.171.124 does not build on Windows with GHC 7.6.1.
It breaks for fresh installs with users who have Cabal-1.6.0 rather than Cabal-126.96.36.199, ie users of ghc-7.6.1.
Fall back to using serial rather job control for base < 4.3. So this means if you build caba-install with ghc-6.12 or older then the -j flag will do nothing, it'll still run serially. BTW, if anyone wants to build cabal-install using a Haskell impl with no support for concurrency then they can use the same trick. (The serial and parallel job control impls deliberately share the same interface.)
By default, "cabal unpack blah" will also update the .cabal file with the one from the index, so it's consistent with what you get via cabal install. Also added a --pristine flag so you can get the original tarball without the updated .cabal file.
(patch manually merged into the cabal-1.16 branch) This allows us to make minor changes to packages after they have been released, without changing the package .tar.gz file. We already keep the .cabal file outsite the package in the index and use it for dependency planning. This already lets us do fixes such as making dependency constraints tighter. Currently we cannot make dep constraints more relaxed however, since the original .cabal file is the one used when we get to the actual configure step. So with this change, we now use the updated .cabal file for the configure and build too. So there's more fixes we can do post-release. In particlar, in combination with easier editing on hackage, this should help us address the problems around the PVP and open or closed version constraints. It should allow a system of conservative upper bounds, but allow editing them when new versions of deps are released and we find that they happen to work fine.
This was broken in 5f50fb1: Instead of a vanilla version, the code would build a profiling version of the objects for TH.