Currently opam-builder considers that any package whose dependencies are installable should be buildable, and counts any failure as just a Failure of the package to build. This PR separates two status, Failure, when the package itself fails to build, and DepFail (Dependency Failure), when one of the dependencies failed to build. Separating the two in the web interface really matter if we want to locate the packages that have to be fixed first -- currently I waste time going through Failure that are in fact DepFail, and (for now) require no action on my part.
Currently opam-builder considers that any package whose dependencies are installable should be buildable, and counts any failure as just a Failure of the package to build. This PR separates two status, Failure, when the package itself fails to build, and DepFail (Dependency Failure), when one of the dependencies failed to build. Separating the two in the web interface really matter if we want to locate the packages that have to be fixed first -- currently I waste time going through Failure that are in fact DepFail, and (for now) require no action on my part.
Fixes #5.