GitLab

kristenk authored Mar 18, 2018 and Mikhail Glushenkov committed May 09, 2018

CABAL_DIR can be used to run integration tests independently on Windows,
since setting HOME doesn't affect the location of the APPDATA directory.

Before there wasn't much feedback. Most times the only thing that got
printed was "Up to date".

See #4737

[ci skip]

And error if they are explicitly enabled, so we never try to install
remote packages with tests and/or benchs.

Fixes #4855

The PackageId and ComponentName are already part of the existing
AvailableTarget record argument.

We need to eliminate this redundancy because for new kinds of target
selectors we will not have the PackageId and ComponentName from the
selector, only from the AvailableTarget selected.

Add TargetPackageNamed, like TargetPackage but for known packages
within the project that are only specified by name. This includes the
extra-packages from the @cabal.project@ file.

It does not include indirect deps or other packages from hackage. That
will be covered by a separate constructor.

This replaces the previous TargetPackageName constructor which was part
of a much more limited implementation of the same general idea.

Previously the TargetSelector type had a type param for the type of the
package that it referred to. In particular we used it with types like:

type Matcher  = ... -> Match (TargetSelector KnownPackage)
type Renderer = TargetSelector PackageId -> ...

However we are about to extend the TargetSelector so that it does not
just refer to one form of package (e.g. KnownPackage) but can refer to
packages via various different forms and partial information. So it no
longer makes sense to have TargetSelector be paramaterised by the
different states of the one kind of package it refers to, as there are
now many kinds. So in preparation for that we simplify it so that it is
equivalent to always using TargetSelector PackageId, and we remove the
type paramater.

Add the first part of the new-install command: nonlocal exes.

See #4558 for the design concept.

This part of the command installs executables from outside of a project
(ie from hackage) in the store and then symlinks them in the cabal bin
directory.

This is done by creating a dummy project and adding the targets as extra
packages.