cabal-install-parsers alternatives and similar packages
Based on the "cabal" category.
Alternatively, view cabal-install-parsers alternatives based on common mentions on social networks and blogs.
cabal-fmtAn experiment of formatting .cabal files
cabal-planLibrary and utility for processing cabal's plan.json file
cabal-editA utility for managing Hackage dependencies and manipulating Cabal files from the command line.
cabal-appimageCabal support for creating AppImage applications
cabal-bundle-clib[Moved to: https://github.com/IsumiF/cabal-bundle-clib]
Access the most powerful time series database as a service
Do you think we are missing an alternative of cabal-install-parsers or a related project?
haskell-ci - CI generator for multiple GHC versions
At the moment
haskell-ci support GitHub Actions workflow generation.
There is also legacy Travis-CI configuration generator, which is unmaintained.
haskell-ci relies on
ghcup to install GHC
GHC-7.0.1 — GHC-9.2.1 are supported.
Step 1: Clone and install this project in/from any directory
$ git clone https://github.com/haskell-CI/haskell-ci.git $ cd haskell-ci $ cabal new-install haskell-ci:exe:haskell-ci
```bash cabal new-install haskell-ci ```
Step 2: Change directories to your project:
$ cd path/to/your-project
Step 3: Edit your project's
*.cabalfile to add a
Tested-Withline, such as this one:
$ cat your-project.cabal ... Tested-With: GHC ==8.6.3 || ==8.4.4 || ==8.2.2 ...
Add as many or as few GHC versions to test as you want.
Step 4: Generate a workflow file for your project:
$ # You run the following command from your project's directory, even $ # though it references the script from the `haskell-ci` project $ haskell-ci github your-project.cabal
Note: If you have multiple local Cabal projects that you wish to build together using a
cabal.projectfile, pass that file to haskell-ci instead:
$ haskell-ci github cabal.project
haskell-citool looks at the
Tested-Withline in your
*.cabalfiles and generates a configuration that tests each compiler version you listed in parallel.
Step 5: Create a branch with your new CI configuration file and push your branch:
$ git checkout master # Check out `master` $ git pull --ff-only # Get the latest version of `master` $ git checkout -b new-ci # Create a `new_travis` branch $ git add . $ git commit -m "New CI script" $ git push -u origin new-ci # Push your branch upstream
Step 6: Fix the build
If you're lucky, your repository will build for every compiler version you listed. If that's the case, then just merge your changes into
$ git checkout master $ git merge new-ci # Update `master` with your new CI script $ git push
You can also merge your branch into
masterfrom Github's pull request view.
If you're not lucky, then your new CI branch will fail for one or more versions of GHC, which is okay! Look at the build and fix any build failures you find and commit the fixes to your branch:
$ # Fix any build failures you find and commit your changes $ ... $ git push # Push your branch updates upstream
Sometimes you may need to regenerate CI script, for example, when adding new compiler version to
tested-with. You may simply run