From 0ac0354d67768d0b2714787acfbc2ade9725365a Mon Sep 17 00:00:00 2001 From: Jens Petersen Date: Mon, 29 Jun 2026 14:24:49 +0800 Subject: [PATCH] remove all no-revision packages I do not see any reason for them to exist permanently. I don't feel upstreams should be able to decide whether Stackage uses revisions or not for their package: they are used by cabal-install anyway. Obviously from time to time this may be a useful tool if a revision conflicts with stackage's bounds but it should not be a permanent lever IMHO. --- build-constraints.yaml | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/build-constraints.yaml b/build-constraints.yaml index c8661a02..bc42a898 100644 --- a/build-constraints.yaml +++ b/build-constraints.yaml @@ -9368,22 +9368,12 @@ hide: - zip # conflicts with Codec.Archive.Zip in zip-archive -# Experimental: packages where Hackage cabal file revisions should be ignored. +# Packages where Hackage cabal file revisions should be ignored. # # This always use the cabal file shipped with the sdist tarball instead of the latest revision. # # This only supports pinning to the initial release (revision 0), not to an arbitrary revision. -no-revisions: -- mime-mail -- basement -- cryptonite -- foundation -- gauge -- http-download -- rio-prettyprint -- hi-file-parser -- aura -- hoogle # https://github.com/commercialhaskell/stackage/issues/7496 +no-revisions: [] # Note, this no longer actually does anything with curator2 unfortunately: # Do not build these packages in parallel with others. Useful for high memory