Simplify a few InstallPlan utils, and use setup deps in a few places

When setup deps were introduced "Add ComponentSetup to ComponentDeps", we
kept all uses to be the same old deps, without changing anything by using
those new setup deps. In several places in InstallPlan it makes sense to
use all deps, including setup deps. In fact for InstallPlan we should always
use all deps except in one place: in checking plan validity where we check
for dependency inconsistencies. That's the one place where we look only at
"normal" non-setup deps to check that we're using only one version of each
package.

So for example, with this patch the freeze command now includes setup deps
in the frozen set. The other case that should change is that failures of
deps of packages used only for setup scripts should now be handled properly
because we will look at setup dep edges when looking for things that depend
on a failed package.

Simpler, simpler versions now exist in the InstallPlan module. Those
ones are simpler because they can use the cached Graph.

These are also easy to implement based on the Graph in the InstallPlan.

Not currently used, but will be eventually.

We can calculate this directly on the Graph inside the InstallPlan
rather that using a more complicated algorithm on the PlanIndex.

This patch is primarily motivated by further changes to simplify
and remove dead code from the PlanIndex module.

Use global db in travis

Add some missing extensions to Language.Haskell.Extension

Signed-off-by: Austin Seipp <aseipp@pobox.com>

Migrate integration tests to shell based format, fixed travis

Backwards compatibility type synonym for InstalledPackageId.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

- findExecutable sh
- Use single quotes for cabal exec

bardur.arantsson authored 9 years ago and Oleg Grenrus committed 9 years ago

Fixes #2797

Squashed commits:
- Use ., not source

bardur.arantsson authored 9 years ago and Oleg Grenrus committed 9 years ago

This is required for the reworking of integration tests
to use shell scripts.

cabal haddock: add --for-hackage flag

Always warn when 'cabal install' cannot find a dependency

Use configured compiler for cabal sandbox hc-pkg

Fix #2804: Text Platform roundtrip (with tests)

The GHC[JS]_PACKAGE_PATH and CABAL_SANDBOX_PACKAGE_PATH environment
variables contain colon-separated lists of package DBs, so it doesn't
make sense to call doesDirectoryExist on the colon-separated list.
Instead, this just checks for the existence of the sandbox package DB.