Loosen bounds of snap-templates

haskell-infra / hackage-trustees

Issue tracker for Hackage maintainance and trustee operations

https://hackage.haskell.org/packages/trustees/

42 stars 7 forks source link

Loosen bounds of snap-templates #372

Closed tomjaguarpaw closed 1 year ago

tomjaguarpaw commented 1 year ago

snap-templates has too restrictive upper bounds that stop it compiling on anything >= GHC 8.6, but --allow-newer seems to work fine. This succeeds:

cabal install snap-templates --with-ghc ghc-9.6 --allow-newer

This has caused a problem in real life. At least template-haskell needs to be bumped. I didn't check others.

andreasabel commented 1 year ago

There is an issue in the project's bug tracker from 2020, apparently the maintainers have lost interest:

https://github.com/snapframework/snap-templates/issues/22

andreasabel commented 1 year ago

This is my suggestion for a revision that will at least not be too restrictive for the next couple of years:

Changed the executable 'snap' component's library dependency on 'bytestring' from >=0.9.1 && <0.11 to >=0.9.1 && <1
Changed the executable 'snap' component's library dependency on 'containers' from >=0.3 && <0.7 to >=0.3 && <1
Changed the executable 'snap' component's library dependency on 'hashable' from >=1.1 && <1.2 || >=1.2.0.6 && <1.3 to >=1.1 && <2
Changed the executable 'snap' component's library dependency on 'template-haskell' from >=2.2 && <2.15 to >=2.2 && <3
Changed the executable 'snap' component's library dependency on 'text' from >=0.11 && <1.3 to >=0.11 && <3

tomjaguarpaw commented 1 year ago

Thank you @andreasabel. I'm not a user of this package myself (I'm just reporting the breakage reported in the Reddit post) so I don't have an opinion on the risks due to too-loose upper bounds. Please take whatever action you deem most appropriate.

andreasabel commented 1 year ago

If there is no material interest in a package, we shouldn't waste our time in bumping bounds for maintainers in sleeping pill mode. There are 15.000 packages on Hackage of which likely 10.000 are trash. Can spend an eternity on this trash.

I wish Hackage had a coloring scheme that would alert users clearly that they are looking at trash. Currently you have to have close look at the list of dependencies, know current versions of these by heart and then don't be fooled by the lack of hackage to properly interpret conditionals when displaying dependencies.

andreasabel commented 1 year ago

Published these bumps to major-major upper bounds.

tomjaguarpaw commented 1 year ago

Thanks, I appreciate it.