On 5 Jan 2014, at 10:15, Mateusz Kowalczyk wrote:
It seems that we are having a rather big issue with Hackage in recent
months and I'm sure many of you have noticed: a lot of packages aren't
getting their docs built. As far as I can tell, there can be multiple
reasonable causes:
*
Oops, seems I sent to libraries. Let's keep the thread on cabal-devel
only as here's where the replies happened.
On 06/01/14 10:27, Malcolm Wallace wrote:
On 5 Jan 2014, at 10:15, Mateusz Kowalczyk wrote:
It seems that we are having a rather big issue with Hackage in recent
months and I'm
Hi David,
Great to here that you're going to hack on cabal. We need all the
contributors we can get!
The general roadmap for 1.20 is here:
http://www.haskell.org/pipermail/cabal-devel/2013-September/009533.html
The Do the right thing automatically section is probably the most newbie
friendly.
On 6 Jan 2014, at 12:32, Henning Thielemann wrote:
Am 06.01.2014 12:59, schrieb Mateusz Kowalczyk:
On 06/01/14 10:27, Malcolm Wallace wrote:
Haddock also was once stand-alone. I think it might be time to wind the
clock backwards and retrieve this desirable property.
Was Haddock ever
On Mon, Jan 6, 2014 at 5:27 AM, Malcolm Wallace malcolm.wall...@me.comwrote:
I think the fundamental problem is that Haddock is now built on top of
ghc. So if a package cannot be built by ghc (for whatever reason, e.g.
missing C library dependency), then it cannot be documented either. This
On Mon, Jan 6, 2014 at 3:33 PM, Brandon Allbery allber...@gmail.com wrote:
On Mon, Jan 6, 2014 at 5:27 AM, Malcolm Wallace malcolm.wall...@me.comwrote:
I think the fundamental problem is that Haddock is now built on top of
ghc. So if a package cannot be built by ghc (for whatever reason,
Thank you, this worked like a charm! (Modulo using dist/doc/html
instead of dist/doc). Now all my packages have online documentation.
One day I'd still like to find out why it didn't build automatically.
But as long as documentation builder doesn't generate a log saying
what problem it thought
i'm sure patches are welcome to improve hackage infrastructure in these
ways! :)
On Mon, Jan 6, 2014 at 3:00 PM, Peter Selinger selin...@mathstat.dal.cawrote:
Thank you, this worked like a charm! (Modulo using dist/doc/html
instead of dist/doc). Now all my packages have online documentation.
On 05/01/14 10:15, Mateusz Kowalczyk wrote:
Hi all,
It seems that we are having a rather big issue with Hackage in recent
months and I'm sure many of you have noticed: a lot of packages aren't
getting their docs built. As far as I can tell, there can be multiple
reasonable causes:
[snip]
Mateusz, thanks for the great sleuth work and communication on this.
I'm working on fixing my missing docs (hledger*, broken due to
pretty-show requiring a newer-than-default happy executable).
___
cabal-devel mailing list
cabal-devel@haskell.org
Thanks, that's even better!
However, I find that the --contents-location option to cabal haddock
does not work properly. Apparently it not only prevents index.html
from being built (which makes modest sense), but it also prevents
index-frames.html from being built (which does not). So in the
On 07/01/14 01:23, Peter Selinger wrote:
Thanks, that's even better!
However, I find that the --contents-location option to cabal haddock
does not work properly. Apparently it not only prevents index.html
from being built (which makes modest sense), but it also prevents
index-frames.html
Hi Mateusz,
of course you could do the same thing with a bash script. It's a
matter of personal taste and workflow. Just for the record, you can
pass arguments into a Makefile like this: make PACKAGE=bla. And $$
is indeed an escape, to denote a literal dollar sign (as opposed to a
Makefile
13 matches
Mail list logo
