GitLab

This addresses most of ticket #206.

Will make it easier to create the bin dir, if that's what we want to do.

No flag to turn it on/off yet.

Split BuildResult into Either BuildFailure BuildSuccess
Make BuildSuccess contain info for docs and tests.
Make PlanPackage use BuildSuccess and BuildFailure directly
rather than being parameterised by any build result type.
This has a knock on effect on lots of other types which
were parameterised just because PlanPackage was.

And make the parsing slightly nicer.

We can remove the local copy once we switch to the next
Cabal version. In the mean time, the code is at least sane
and consistent between libs.

use the pre-existing ppFields

Really it should be eleminated entirely.

I introduced a subtle bug with paths when I stopped using inDir
outside of setupWrapper. It was using the current dir to find
Setup.hs rather than the target dir. That ofen works because
there's a Setup.hs in the local dir. I think it's now fixed to
always use paths relative to workingDir. As before, it invokes
the setup binary giving it the new working dir.

This is the groundwork needed to support local repositories,
that is ones acessable via the local filesystem and without
a corresponding download cache. They use the same format/layout
as the download cache of a remote repo.

and link it up with the symlink feature code.

This covers the major part of ticket #289.

Now uses a single code path for both modes.

Eg can use cabal install foo --log-builds='$pkgid-$compiler.log'
and the build log for each package will written to a separate
file. If an existing file is given then the log is appended.
This or something like it should help in future with build
reporting of the non-anonymous kind.

The path to the binary we're running must be accessable from
that other directory. The fix is to use currentDir </> setup

Rather than calling inDir directly.

For the internal method, change to the right working dir if necessary.

Except for optionDryRun which is shared with another command.