cabal-fmt
hackage-trustees
Our great sponsors
| cabal-fmt | hackage-trustees | |
|---|---|---|
| 2 | 7 | |
| 104 | 42 | |
| - | - | |
| 4.8 | 0.0 | |
| about 2 months ago | almost 2 years ago | |
| Haskell | ||
| BSD 1-Clause License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cabal-fmt
-
Is there some truth to this hyperbole? "Haskell is beautiful and elegant, but unmaintainable and painful"
It kinda is, but it's a one-time thing and it gives us the ability to map module names to packages by only looking at the index. Plus, the list can be generated: cabal-fmt has an expand feature, and in the future HLS could do that too.
-
Is there a prettifier for Cabal files?
https://github.com/phadej/cabal-fmt is pretty widely used. I think there's also a VSCode extension for it.
hackage-trustees
-
Is there some truth to this hyperbole? "Haskell is beautiful and elegant, but unmaintainable and painful"
If the version bound is actually too strict there's no need to fork, you can just build with --allow-newer while you wait for upstream. In case upstream is unresponsive, hackage trustees can step in and update the bound.
-
Cabal package download 403 error
Hackage trustees (https://github.com/haskell-infra/hackage-trustees/) probably can't do anything with the "backend" / infrastructure; they are mainly concerned with package info / metadata revisions.
-
Cabal not resolving dependencies
If this bound relaxation works for you, please PR digestive-functors-aeson. If the package is unmaintained, PR it anyway and file an issue at the Hackage Trustees Issue Tracker requesting a metadata revision on Hackage.
-
[ANN] GHCup 0.1.17 release
Unfortunately it's blocked by https://github.com/haskell-infra/hackage-trustees/issues/310
-
Thoughts on this??? Not my tweeter account.
The Hackage Trustees policy says
-
Talk about new random's interface
The relevant Trustees policy document is https://github.com/haskell-infra/hackage-trustees/blob/master/policy.md#2-metadata-only-changes-relaxing-constraints
What are some alternatives?
cabal-edit - A utility for managing Hackage dependencies and manipulating Cabal files from the command line.
stackage - Stable Haskell package sets: vetted consistent packages from Hackage
cabal-plan - Library and utility for processing cabal's plan.json file
bazel-coverage-report-renderer - Haskell rules for Bazel.
cabal-install-parsers - Scripts and instructions for using CI services (e.g. Travis CI or Appveyor) with multiple GHC configurations
scoop-better-shimexe - A better shim.exe file for Scoop.
cabal-bundle-clib - [Moved to: https://github.com/IsumiF/cabal-bundle-clib]
cabal-cache - CI assistant
cabal-appimage - Cabal support for creating AppImage applications
haskell-language-server - Official haskell ide support via language server (LSP). Successor of ghcide & haskell-ide-engine.
Cabal - Official upstream development repository for Cabal and cabal-install