-
Notifications
You must be signed in to change notification settings - Fork 697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cabal new-haddock
fails for build-type:configure
#5503
Milestone
Comments
This is related to #5261 which fixed the same symptom for |
@alexbiehl suggests the culprit to be
missing the logic from
|
chshersh
pushed a commit
that referenced
this issue
Sep 7, 2018
hvr
added a commit
to hvr/cabal
that referenced
this issue
Sep 8, 2018
…nfigure` In the course of 4466310 (see haskell#5526) the `Setup.hs haddock` CLI was extended to allow component ids to be passed as positional arguments. However, `autoconfUserHooks` which is used in case of `build-type: Configure` wasn't updated accordingly, and consequently this caused `new-haddock` to break for packages using `Configure`. Fixes haskell#5503
hvr
added a commit
to hvr/cabal
that referenced
this issue
Sep 8, 2018
…nfigure` In the course of 4466310 (see haskell#5526) the `Setup.hs haddock` CLI was extended to allow component ids to be passed as positional arguments. However, `autoconfUserHooks` which is used in case of `build-type: Configure` wasn't updated accordingly, and consequently this caused `new-haddock` to break for packages using `Configure`. cc @alexbiehl Fixes haskell#5503
hvr
added a commit
that referenced
this issue
Sep 8, 2018
…nfigure` In the course of 4466310 (see #5526) the `Setup.hs haddock` CLI was extended to allow component ids to be passed as positional arguments. However, `autoconfUserHooks` which is used in case of `build-type: Configure` wasn't updated accordingly, and consequently this caused `new-haddock` to break for packages using `Configure`. cc @alexbiehl Fixes #5503 (cherry picked from commit 86dabda)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reproduction:
using
-v
reveals:The text was updated successfully, but these errors were encountered: