Dominic Steinitz | 16 Dec 20:31

Build Log Question

I was about to update the crypto package when I noticed that there is
now a "build log" on each package page.

What does this mean and what should I do as package maintainer?

Many thanks, Dominic.

>> Step 1 - configuring Crypto-3.0.3
> 
> Configuring Crypto-3.0.3...
> Setup.hs: At least the following dependencies are missing:
>     NewBinary -any
> 
>>> Terminated due to an error.

>>> Step 1 - configuring ASN1-0.0.1
> 
> Configuring ASN1-0.0.1...
> Setup.hs: At least the following dependencies are missing:
>     NewBinary -any
> 
>>> Terminated due to an error.
Duncan Coutts | 17 Dec 11:23

Re: Build Log Question


On Sun, 2007-12-16 at 19:34 +0000, Dominic Steinitz wrote:
> I was about to update the crypto package when I noticed that there is
> now a "build log" on each package page.
> 
> What does this mean and what should I do as package maintainer?

It means there's a package builder that will try building your package
after you upload it. It'll generate haddock documentation this way.

Some build problems are not easy for you to prevent, like missing C
libs. In this case NewBinary failed to build (due to a mistake in
NewBinary's haddock markup) so Crypto also fails to configure.

At the moment the package build stuff is not especially helpful to you
as a package maintainer since it only gives you feedback after you've
made the release and it doesn't automatically email anyone.

Duncan

Gmane