Now when using CPP you get 

   MIN_VERSION_<package>(A,B,C)

for each <package> in build-depends, which is true if the version of
<package> in use is >= A.B.C, using the normal ordering on version
numbers.

This is done by auto-generating a header file
dist/build/autogen/cabal_macros.h, and passing a -include flag when
running CPP.

Since it is shared between libs and exes. Extend the documentation
to describe the syntax of version constraints, including the new
version range syntax "build-depends: foo ==1.2.*".

Change to runhaskell Setup or cabal-install as appropriate.

It doesn't need to be right up near the top.

in one of the fields exposed-modules, other-modules or main-is
Add an extra note to the section on the Paths_pkgname module
as the fact that it's automatically generated confuses people.

The user guide gets built in two different ways. There's a target
in Cabal's the top level Makefile and there is also the stuff that
the ghc build system uses. The ghc build system expects to copy in
doc/fptools.css and then delete it again on make clean. We want a
persistent copy so that we can make the docs when we've just got a
standalone Cabal build tree, so that's now kept as doc/Cabal.css.

Though they actually only take one dir each so perhaps they should be
renamed to just --extra-include-dir and --extra-lib-dir. You can of
course use them multiple times to get a list of dirs.

and a couple other trivial tidyups

to $HOME/.cabal on unix and on WinXP: (not sure about vista)
C:\Documents And Settings\user\Application Data\cabal

Fixes ticket #11. Though the section could do with a bit more detail.
It corresponds to what's on the wiki:
http://hackage.haskell.org/trac/hackage/wiki/StableInterfaces

Spotted by Spencer Janssen

Describe the new syntax and make variuous changes to the
description of the meaning.

and remove makefile --ghc-option flag as it's not used (as far as I can see).
It works generically by updating the ProgramConfiguration rather than the
previous ad-hoc implementation. This feature is generally only useful for
hackers who want to pass extra args to a progam during the build step
(probably as a one-off) without having to reconfigure.