Helped extra-ghci-libraries find its way to .cabal files.
error if the config file is invalid

This stops surprising the developer when their config file is ignored due to a typo.
switched from error to die
Typos.

Thanks to A. Bram Neijt (see #2045).
-Wall police.
Improve an error message.
'loadConfig': don't set haddockProgram[Args,Paths].

This information is passed via 'dist/setup-config'.

See https://github.com/haskell/cabal/issues/2046#issuecomment-53034455.
Accommodate network/network-uri split
Merge pull request #2053 from RyanGlScott/master

Accommodate network/network-uri split
.travis.yml: Bump GHC version.
Bump version.

So that the 'install_from_tarball' build bot step doesn't try to use the old
1.21 snapshot that comes with GHC HEAD.
Apply network-uri split to test package as well.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
A few more sandbox related ignore items.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
Actually check for command success in these tests

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
Merge pull request #2059 from ezyang/ezyang-test-fixes

Ezyang test fixes
Change the inplace package database to not use file-style database.

Instead we use HcPkg.init (e.g. ghc-pkg init). For ghc-pkg this will
create a new directory style db.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
Signed-off-by: Duncan Coutts <duncan@well-typed.com>
Suppress orphan warning pre-GHC 7.8

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
Fix ABI hash construction to exclude trailing newline
Change rep of module re-exports, and do resolution ourselves

The initial support for module re-exports relied on ghc-pkg to resolve
user-specified re-exports to references to specific installed packages.
This resolution is something that can fail so it's better for Cabal to
do it during the package configure phase.

In addition, it is inconvenient in ghc-pkg to be doing this resolution,
and it just seems fishy as a design. Also, the same ModuleExport type
was being used both for user-specified source re-exports and also for
the specific re-exports in the package db.

This patch splits the type into two: one for source level, and one for
resolved ones for use in the package db. The configure phase resolves
one to the other.

One minor change: it is now possible to re-export a module defined in
the same package that is not itself exported (ie it's in other-modules,
rather than exposed-modules). Previously for modules definied in the
same package they had to be themselves exported. Of course for
re-exports from other packages they have to be exposed.
Add extra network dependency to make sure dep solver gets it right.

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