Ticket #56 (new enhancement)

Opened 7 years ago

Last modified 4 years ago

hackageDB should not accept a package if it is not installable

Reported by: ijones Owned by:
Priority: normal Milestone: HackageDB
Component: hackageDB website Version:
Severity: normal Keywords:
Cc: Difficulty: normal
GHC Version: 6.2.1 Platform: Linux

Description

hackageDB should try to build and install each package in a chroot before "accepting" the package. If it doesn't build, it should email the uploader or maintainer.

Change History

Changed 6 years ago by ross@…

  • platform set to Linux
  • ghcversion set to 6.2.1
  • type changed from defect to enhancement

Changed 6 years ago by guest

The is hard, because you may need to install C devel libraries. Also, it means running arbitrary code unless it is restricted to main=defaultMain and we ensure no extensions like TemplateHaskell? will be used, either by the .cabal file or by an options pragma. And you may need a particular (possibly darcs) version of a particular implementation.

Changed 5 years ago by duncan

One option here is to put newly uploaded packages into a separate category and not move them over into the main repo until there are some number of successful build reports. This would depend on hackage/cabal-install build reporting (ticket #184).

That'd reduce the load on a central hackage server.

Changed 5 years ago by duncan

An example we could automatically discover: AutoForms?-0.4 requires syb-with-class>=0.4 but the latest version of syb-with-class in hackage at the moment is 0.3.

Changed 5 years ago by duncan

  • milestone changed from Cabal-1.4 to Cabal-1.6

Not ready for this release, punting.

Changed 5 years ago by duncan

  • milestone changed from Cabal-1.6 to HackageDB

Changed 4 years ago by SamB

What if hackage doesn't have the right compiler?

Note: See TracTickets for help on using tickets.