| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
It's a bit heavy just for a single use-site for debugging.
|
| |
|
| |
|
|
|
|
|
| |
After lamenting the fact that we don't have this in the docs I figured it
really ought to be an exposed abstraction.
|
|
|
|
|
| |
Unfortunately we need this to pass a custom GHC executable path to stack,
since it doesn't have an option to override it on the commandline (yet?).
|
|
|
|
|
| |
We need to support passing down the path to ghc to new-build/stack in order
to support using a non-default 'ghc' executable.
|
|
|
|
|
|
|
|
|
| |
I'm turning off -Wunused-imports in the modules that have to deal with
ancient Cabal versions because maintaining warning cleanlyness really is
quite pointless when you have to deal with all sorts of deprecations and
stuff moving around. I don't think having too many imports will ever break
anything there unless the modules really get deprecated and removed, but
we'll notice that ;)
|
|
|
|
|
| |
In turn fixes errors when building cabal-helper exe for stack projects
where the resolver uses a different ghc version than system.
|
| |
|
| |
|
|
|
|
|
| |
Add list of components to Unit data type to handle v2 based builds
per cabal unit.
|
| |
|
| |
|
| |
|
|
|