Skip to content

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also .

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also .
Commits on Sep 29, 2012
@dcoutts dcoutts On install, update the .cabal file with the one from the index
(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.
@dcoutts dcoutts Extend the unpack command for the .cabal file updating
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.
Commits on Oct 02, 2012
@tibbe tibbe Bump Cabal version number to ebc9124
@tibbe tibbe Bump cabal-install version number to 1.16.0 5ea2203
Commits on Oct 03, 2012
@tibbe tibbe Update bug tracker location 7d6b527
@dcoutts dcoutts Fix building cabal-install with ghc-6.12 and older
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.)
Commits on Oct 05, 2012
@dcoutts dcoutts Disable setting the jobs: $nprocs line in default ~/.cabal config
It breaks for fresh installs with users who have Cabal-1.6.0
rather than Cabal-, ie users of ghc-7.6.1.
@asr asr Fixed warnings on the generated Paths module.
The warnings are generated by the flag '-fwarn-missing-import-lists'.
Commits on Oct 07, 2012
@tibbe tibbe Fix compilation error 41e9d1e
Commits on Oct 11, 2012
@tibbe tibbe Bump network dependency in to
network- does not build on Windows with GHC 7.6.1.
@tibbe tibbe Merge branch 'cabal-1.16' of into cabal-…
@tibbe tibbe Bump Cabal version number to 2afcbb5
@tibbe tibbe Bump cabal-install version number to e99e308
@tibbe tibbe Change to require Cabal >= 1.16 && < 1.18 6c5d844
Commits on Oct 13, 2012
@snoyberg snoyberg Fix installing from custom folder on Linux (#1058) 48082b9
Commits on Oct 24, 2012
@tibbe tibbe Have use Cabal- e1912a3
Commits on Nov 06, 2012
@tibbe tibbe Revert "Fixed warnings on the generated Paths module."
This commit breaks the path module on Windows.

This reverts commit df6fe40.
@tibbe tibbe Bump Cabal version number to 9e72399
@tibbe tibbe Add missing modules in test-suite section
Fixes #1102
Commits on Nov 07, 2012
@tibbe tibbe Bump Cabal preferred version to 2f916fb
@tibbe tibbe Bump cabal-install version number to 87b7129
Something went wrong with that request. Please try again.