#184: cabal-install should report build results to hackage server ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: reopened Priority: high | Milestone: Component: cabal-install tool | Version: 1.2.2.0 Severity: normal | Resolution: Keywords: | Difficulty: project(> week) Ghcversion: 6.4.2 | Platform: Linux ---------------------------------+------------------------------------------ Comment (by duncan): Replying to [comment:1 duncan]:
There are various sub-tasks:
* Make cabal install not fail overall just because one package fails. There should be a mode to carry on and build all remaining packages that did not depend on the failed package. This requires keeping a full dep graph while installing, not just a linear list of packages. * Define a build report data type * Generate a build report for each * Collect build reports in a local file
* Upload build reports to hackage at appropriate points. Perhaps new reports should be sent at the same that the package index or tarballs are downloaded. * Implement server side script to allow reports to be uploaded. Have to decide where and how reports are stored. Obvious choice is a log file per
* Implement the statistical analysis necessary to distill the reports into useful information per-package. Present this info on each package
These are all now done. Build reports are logged into `~/.cabal/packages/$server/build-reports.log`. package-version. Or some other kind of data base and index. The considerations here are in keeping the reports anonymous and what queries we will want to run on the reports. page. These are the remaining tasks. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/184#comment:4 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects