Automatically install necessary build-tools

[snoyberg]

A common user error with cabal is when alex or happy is not available. We should do better: why not install them automatically when they aren't present?

[DanBurton]

Design decision: should we attempt to use what the user has on the path, or should our tool suite always manage its own? The former is more user-configurable. The latter is less stateful and more predictable.

I would say: make the default the latter, provide a config option for the former. I'd say the same goes for ghc and cabal, simply don't use the stuff the user already has unless configured to do so.

[snoyberg]

I like that

On Sat, May 16, 2015, 11:36 PM Dan Burton notifications@github.com wrote:

Design decision: should we attempt to use what the user has on the path,
or should our tool suite always manage its own? The former is more
user-configurable. The latter is less stateful and more predictable.

I would say: make the default the latter, provide a config option for the
former. I'd say the same goes for ghc and cabal, simply don't use the stuff
the user already has unless configured to do so.

—
Reply to this email directly or view it on GitHub
#16 (comment)
.