On Mon, Jul 23, 2007 at 07:55:22AM +0200, Sascha Böhme wrote:
> Should build logs of erroneous packages be mailed to the package
> maintainer?
Definitely.
What does it mean if there are no build logs at all, not even failed?
Why do the docs for functorm 404, when then build log shows success
> Concerning the last question, there is already a list of ideas at [4],
> but maybe more ideas or requests are now arising.
Great work Sascha!
I'd like to be able to:
* recategorise packages online,
e.g. we have "Compilers/interpreters"
"Code generation"
Hello,
HackageDB [1] now contains automatically generated build logs for some
packages, most of them also have automatically generated Haddock
documentation. This is, for now, the result of my Google Summer of Code
project.
The progress of the project can be followed from [2], the sources and
som
Hi Marc,
On Sat, Jul 21, 2007 at 02:26:47AM +0200, Marc Weber wrote:
>
> What about adding another target ./setup plain_source which should
> preprocess everything (including cpp) and output the files to an extra
> directory?
> Why?
> This could be used for haddock documentation generation (Not
> Sounds very cool. *However* the output will not be portable,
It dasen't have to be portable. That's why you have your source
distribution.tar.gz or darcs repa..
I just want a bunch of files which I can feed intto haddock or any
other developement tool (tag generation etc)..
If you need to ref
