haddock after new-repl

[llelf]

Recently cabal started to basically do a haddock build after new-repl.
Is it intentional (or my setup is broken)? It's definitely surprising.

This is what I mean:

$ cat cabal.project
packages: .

package foo
  documentation: True

$ cabal new-repl lib:foo                        --  new-repl

⟨…⟩

Ok, six modules loaded.
Collecting type info for 6 module(s) ... 	--  ghci repl
→ :quit 					--  exit from ghci
Leaving GHCi.
Preprocessing library ⟨…⟩			--  starting haddock build!!!
Running Haddock on library ⟨…⟩
⟨…⟩

[23Skidoo]

Likely because repl and build share the same code path. Agreed that repl shouldn't do this. Is this with 2.2 or only with master?

[alexbiehl]

This might be the result of the recent c094940. Maybe we should disable haddock'ing for repl builds.

[llelf]

@23Skidoo master. But I tried 2.2, the same result.

@alexbiehl new-test too likely. It shouldn't fail because of haddock error, … or is it? Not sure.

[quasicomputational]

I verified that I can reproduce this with 2.2, and that I can't reproduce now on master. Presumably #5226 has fixed it, so closing.