Update HACKING.md

Add `--enable-tests` for cabal-install setup instructions

Exit with an error if $CABAL_SANDBOX_CONFIG does not point to extant file

Add support for automatic profiling detail levels, with reasonable defaults

Support pure test packages (issue #1186)

New flags: --profiling-detail and --library-profiling-detail.
When profiling is enabled (by the existing flags) then these flags
are taken into account to set the profiling detail level.

The levels are:
 none
 default
 exported-functions
 toplevel-functions
 all-functions

The default value for ghc for libraries is exported-functions and
for exes is toplevel-functions.

On GHC these levels correspond to the -fprof-auto* flags. The
ghc-prof-options will override this (just because it's passed to
ghc at the end).

maybeDecompress: bail on all errors at the beginning of the stream with zlib < 0.6

Fix #2704

Code branch with zlib <0.6 cannot recognise the uncompressed input.

Add missing test modules

This commit relaxes D.PackageDescription.Check.checkConfiguredPackage so that it
only warns when a package declares no executables, libraries, tests, or
benchmarks.  Similarly, it relaxes the check during build to only require one
component that is buildable and enabled.  Install now requires an executable or
library.

Use the version macros when building Setup.hs

The design called for allowing deps to be specified, and for the
Setup.hs to be able to use the same version macros as in other code.
This patch completes that second part.

Matthias Fischmann authored 9 years ago and Duncan Coutts committed 9 years ago

Fix: 7.4.2 compat.

PVP compliance: upper version bound.

Revert noise and relax zlib min version back to 0.5.3 (part 1/2).

Revert noise and relax zlib min version back to 0.5.3 (part 2/2).

Test cases for maybeDecompress.

Use edsko's implementation of maybeDecompress; add test case.

Fixup.

maybeDecompress: test suite work-around.

Cleanup.

Relax zlib upper bound.

maybeDecompress: add mysteriously failing test cases.

7.4 compat for test cases.

Warn if GHC{,JS}_PACKAGE_PATH points to non-directory

And add backwards compat support for ghc-7.2 and older that used
the -auto and -auto-all flags.

Simplifies the code in D.S.GHC where we're deciding the options to use.

ttuegel authored 9 years ago and Duncan Coutts committed 9 years ago

Conflicts:
	Cabal/changelog

Merge https support

e.g. cabal install https://example.com/foo-1.0.tar.gz

The initial patch would always try to use HTTPS, even when the repo
specified to use HTTP. This works for the central community hackage
but obviously does not work in general.

The new logic is that we always follow what is specified for the
remote repo in the config, except for built-in known repos (currently
just the central community hackage) where we mark them as also
supporting https. For upload when uploading to such a marked repo
then we will try https and will complain if the plain-http impl was
selected automatically (but it's ok if selected manually).

This patch also changes things so that for http urls on download, we
stick to the builtin http impl by default, and only use the external
ones if https support is required (i.e. because the repo was
configured to use an https url)

Move utils into other Util modules.
Reformat all code to 80 cols.
Reorder code and add more comments.
Use long form style program args, e.g. --silent rather than -s
Finish implementation of form upload with wget
Fix reporting of server error messages for upload (curl & builtin)
Implement collecting of ETags for curl and wget.
Fix wget for case of 304 not modified response (wget uses exit code 8).
Rework transport configuration phase.

gershomb authored 9 years ago and Duncan Coutts committed 9 years ago

Supports both uploading and downloading.
Basic built-in HTTP is still supported.

Get 'builddir' from cabal.config or CABAL_BUILDDIR

This will be useful for adding crypto credentials without people having
to update their config files.

Also useful point to add any other special casing for known repos.

Will need a later check to validate the repo info, e.g. that it's a
supported url scheme and is an absolute URI.