Despite appearances this is actually not completely pointless.
For the Cabal-1.4 branch we need the *Verbose fields to have the
same types as they did in Cabal-1.2, becuase lots of Setup.hs
scripts use them and our change to make them all have type Flag
makes many Setup.hs scripts fail. A solution for the 1.4 branch
is to rename the real field and to add the old field back in.
To keep as much similarity as possible between the HEAD and 1.4
branches I'm applying the name change in both.
On the plus side it's a better name anyway.

And change all uses.

Especially instead of abusing a PackageIdentifier for the purpose.

(pkgName . packageId) and (pkgVersion . packageId)
turn out to be very common so give them names.

Though we'll probably need to do so eventually because they contain many of
the same fields as the .cabal files which are UTF8. This will need agreement
with ghc-pkg.

So we use ordinary read/writeFile for ordinary text files. For console
output we use ordinary putStr etc and we'll just hope that haskell
implementations catch up and deal with that sensibly. Don't assume
captured program output is UTF8, use the default encoding.
So we use binary mode IO along with UTF8 encoding and decoding only for 
file types that we specify to be UTF8, which are .cabal files and
.hs/.lhs files only.

Added readTextFile and writeTextFile which use UTF8. rawSystemStdout now
assumes the programs are producing output in UTF8 encoding.

Also print output and error messages etc in UTF8.

It uses the renaming trick to make the write atomic.
Not yet tested on Windows.

Using 'packageId' seems a bit clearer that it's just the PackageIdentifier 
rather than 'package' which might indicate something containing more info.
contain

New Distribution.Simple.BuildPaths module similar to the .InstallDirs module
to hold all the paths and filenames used during a build.
It's currently somewhat of a miscellaneous collection.

No longer inlcude compatability hacks and remove code that handles
the old style of ghc-pkg package registration files.

And specify command flags in a way that allows converting from or two strings.
So not only can we parse command lines into the various flag types, we can
convert back. This is crucial in cabal-install so that we can call Setup.hs
scripts with all the various args, and override certain flags in a typed way
rather than just representing them all as strings.

This simplifies things and makes it a bit more versatile since
we can use things like InstallDirs (Maybe PathTemplate).

Since it really only refers to haddock interfaces, so interface is too
general a term. Cannot push to 1.2 branch as it changes the api.

This fixes inter-package doc links when building GHC.

We previously had this kind of code all over the place:
> when (verbosity >= verbose)
>      (putStrLn "some message")
We now replace that with:
> info verbosity "some message"
Much nicer.

PackageDB can be user/global or a specific package db. The latter option is
not exposed in the user interface anywhere.
Also move the getInstalledPackages into the per-compiler modules with a
non-compiler-specific wrapper left in Distribution.Simple.Configure

Compiler, Program, PreProcess and Setup are really part of the Simple
build system.
Also move a couple GHC modules under Simple.GHC.*

For includes, don't list the include dir in the package registration
info unless we're actually going to install some include files.
So we should create fewer pointless empty directories. See bug #97.

It's still useless on Windows.

Also make the follow on changes to everything that uses Program.
The notion of a program is now split into the abstract notion of a program
that we know about and might be able to configure, and a configured program
that we can actually run. The ProgramConfiguration database is similarly
split. We still keep user-supplied loation and arguments and use them when
we configure programs. The abstract Program now has functions to search for
the program on the system and for finding the version number. This allows
for more generic configuration of programs.

New types for the collection of installation directory templates and a
separate type for the collection of actual real install FilePaths.
The templates are represented with a PathTemplate adt.
Dir templates can now be relative to each other, eg $htmldir to $docdir
Default install dir templates are now specified compactly in one place.
Adding new dirs should be considerably simpler than previously.
This patch should not actualy change where anything is installed.

It generates the actual file to be passed to the compiler's package program.
This is obviously compiler-specific.