-
Notifications
You must be signed in to change notification settings - Fork 711
what step is needed to get the .tar.gz for uploading haddocks? #5821
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
Comments
|
sdist doesn't run haddock ... what sequence of actions do i need to do go get a haddock targz for then uploading docs to hackage for something which wont build on the hackage environment? goal: i want to be able to do at least with cabal 2.4, theres no mentions of haddocks in v2-sdist. What is the documented way to generate the haddocks into a tar file for upload using cabal? (theres lots of old scripts for doing this, i'm just confused that we have only half of the work flow documented in the cabal CLI ... ) am i overlooking something obvious? |
Oh, that's just me being unable to read. Ignore my response, I don't know the answer off the top of my head. |
here, with bells and whistles on: I agree we should document this better. |
@gbaz I believe that |
does this also produce the targz artifact?
…On Tue, Jan 1, 2019 at 9:16 PM Alec Theriault ***@***.***> wrote:
@gbaz <https://github.com/gbaz> I believe that --haddock-for-hackage now
implies --haddock-hyperlink-source and --haddock-quickjump
<https://github.com/haskell/cabal/blob/c2cf30cc50109f2ffa30fd7affe9c22e1adf922c/Cabal/Distribution/Simple/Haddock.hs#L160-L166>,
so cabal new-haddock --haddock-for-hackage should suffice.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5821 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAQwl1RX-x-_4whhGMYuNSQnPTDucS6ks5u_BZtgaJpZM4ZluyB>
.
|
Yes, it does.
… On Jan 1, 2019, at 6:37 PM, Carter Tazio Schonwald ***@***.***> wrote:
does this also produce the targz artifact?
On Tue, Jan 1, 2019 at 9:16 PM Alec Theriault ***@***.***>
wrote:
> @gbaz <https://github.com/gbaz> I believe that --haddock-for-hackage now
> implies --haddock-hyperlink-source and --haddock-quickjump
> <https://github.com/haskell/cabal/blob/c2cf30cc50109f2ffa30fd7affe9c22e1adf922c/Cabal/Distribution/Simple/Haddock.hs#L160-L166>,
> so cabal new-haddock --haddock-for-hackage should suffice.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#5821 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAAQwl1RX-x-_4whhGMYuNSQnPTDucS6ks5u_BZtgaJpZM4ZluyB>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#5821 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKRHAZIZRWT3kzDhrTCSY_MNeO7RZxUMks5u_BtSgaJpZM4ZluyB>.
|
woot! this is great ... but not discoverable in the upload --help output
... and easy to get lost in the verbose out for v2-haddock
On Tue, Jan 1, 2019 at 9:38 PM Alec Theriault <[email protected]>
wrote:
… Yes, it does.
> On Jan 1, 2019, at 6:37 PM, Carter Tazio Schonwald <
***@***.***> wrote:
>
> does this also produce the targz artifact?
>
> On Tue, Jan 1, 2019 at 9:16 PM Alec Theriault ***@***.***>
> wrote:
>
> > @gbaz <https://github.com/gbaz> I believe that --haddock-for-hackage
now
> > implies --haddock-hyperlink-source and --haddock-quickjump
> > <
https://github.com/haskell/cabal/blob/c2cf30cc50109f2ffa30fd7affe9c22e1adf922c/Cabal/Distribution/Simple/Haddock.hs#L160-L166
>,
> > so cabal new-haddock --haddock-for-hackage should suffice.
> >
> > —
> > You are receiving this because you authored the thread.
> > Reply to this email directly, view it on GitHub
> > <#5821 (comment)>,
or mute
> > the thread
> > <
https://github.com/notifications/unsubscribe-auth/AAAQwl1RX-x-_4whhGMYuNSQnPTDucS6ks5u_BZtgaJpZM4ZluyB
>
> > .
> >
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub <
#5821 (comment)>, or
mute the thread <
https://github.com/notifications/unsubscribe-auth/AKRHAZIZRWT3kzDhrTCSY_MNeO7RZxUMks5u_BtSgaJpZM4ZluyB
>.
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5821 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAQwpK8OhsqSbve_wYH_8pURO8Qenxlks5u_BuVgaJpZM4ZluyB>
.
|
This doesn't seem to be documented anywhere, but implicit in the help messages for upload. WHere do i look to find this information?
The text was updated successfully, but these errors were encountered: