hackageDB should not accept a package if it is not installable #63

Closed
bos opened this Issue May 24, 2012 · 6 comments

2 participants

@bos
Haskell member

(Imported from Trac #56, reported by @syntaxpolice on 2006-01-24)

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.

@bos
Haskell member

(Imported comment by guest on 2006-01-24)

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.

@bos
Haskell member

(Imported comment by @dcoutts on 2007-05-26)

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.

@bos
Haskell member

(Imported comment by @dcoutts on 2008-01-12)

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.

@bos
Haskell member

(Imported comment by @dcoutts on 2008-02-21)

Not ready for this release, punting.

@bos
Haskell member

(Imported comment by @samb on 2008-03-12)

What if hackage doesn't have the right compiler?

@tibbe
Haskell member

Closing as there's been no activity in years.

We're cleaning up the bug tracker to make it useful again and are thus closing bugs that haven't seen any activity in a long time. Please re-open (or file a new bug) if the problem reappears.

@tibbe tibbe closed this May 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment