GitLab

Fixes setting the --prefix from the command line which was previously being
ignored in favour of the default prefix from the config file.

eg, currently it is "cabal-install/0.4.2"

Though do display it at deafening verbosity level.

This time to better handle parsing and warning about invalid proxy uris

Simpler and simplifies the Command api in the Cabal lib

Silly #ifdefs making things harder to test.

Which was just being used for an exception-free version of getEnv but we
have to cope with exceptions anyway for the Win32 registry.

On windows, if looking up the info in the registry failed then we failed
overall. Now we just don't use the proxy. Also refactored a bit.

ConfigFlags is not used in any of the modules that do the real work, instead
we just pass in the necessary information. Renamed ConfigFlags to SavedConfig
and moved it's definition into the Config module. Also change what information
is kept in the Repo type so that it knows the local path too. A PkgInfo now
also knows which Repo it is from.

Added support for users behind proxy servers, reading system settings from the env var on unix or registry on windows

cabal upgrade installs the latest version of any currently installed
package.

When installing multiple packages, don't quit just after the first
error, but rather collect the list of packages that failed to install
continue installing whatever packages we can, and provide an error
message at the end.

  "All requested packages already installed. Nothing to do."
rather than:
  "These packages would be installed:\n"
followed by ... nothing.

Use the Distribution.Simple.Utils functions and eliminate use of printf

rather than from the old ~/.cabal-upload/auth file.
Now uses ~/.cabal/config with:
hackage-username:
hackage-password:

Since much recent cabal-install work is his and he wrote cabal-upload which
was just integrated.

It still uses it's own config file, but now uses the same command line stuff

So we now have the complete set of commands in one tool.
This uses the new Command infrastructure to do two way conversion between
flags as strings and as a structured parsed form.

first step to shell command line completion

So don't bother making it a parameter

Use the new cabal command line handling infrastructure. Use proper flag types
rather than strings. 
Drop support for per-package command line flags as it was generally agreed to
be confusing.

ByteString.Char8 treats files as text files, which are really different
on windows. We were getting CRLF translation in Windows which was messing
everything up, like saving & reading the index file.
So now only use BS.Char8 where necessary.

We only have one LICENCE file