cabal uses haddock from hard-coded location
I don't know if this is a feature or a bug. It seems that cabal doesn't search for the haddock executable in $PATH but uses a hard-coded location. Is this the best behaviour? It seems confusing to me. It makes it difficult to upgrade different pieces of the system separately.
Trac metadata
| Trac field | Value |
|---|---|
| Version | 6.8.2 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Build System |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Unknown |
| Architecture | Unknown |