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-fmt

9.2 4.8 cabal-install-parsers VS cabal-fmt

An experiment of formatting .cabal files
cabal-plan

8.7 3.0 cabal-install-parsers VS cabal-plan

Library and utility for processing cabal's plan.json file

InfluxDB - Power Real-Time Data Analytics at Scale

Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

Promo www.influxdata.com

cabal-edit

8.6 0.0 cabal-install-parsers VS cabal-edit

A utility for managing Hackage dependencies and manipulating Cabal files from the command line.
cabal-cache

8.4 4.4 cabal-install-parsers VS cabal-cache

CI assistant
cabal-appimage

2.4 5.3 cabal-install-parsers VS cabal-appimage

Cabal support for creating AppImage applications
cabal-bundle-clib

2.3 0.0 cabal-install-parsers VS cabal-bundle-clib

DISCONTINUED. [Moved to: https://github.com/IsumiF/cabal-bundle-clib]

Do you think we are missing an alternative of cabal-install-parsers or a related project?

Add another 'cabal' Package

Popular Comparisons

cabal-install-parsers

vs

structured-haskell-mode

README

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 hvr-ppa or ghcup to install GHC and cabal-install.

GHC-7.0.1 — GHC-9.2.1 are supported.

Quick-start instructions

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 *.cabal file to add a Tested-With line, 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.project file, pass that file to haskell-ci instead:
```
$ haskell-ci github cabal.project
```
The haskell-ci tool looks at the Tested-With line in your *.cabal files 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 master:
```
$ git checkout master
$ git merge new-ci  # Update `master` with your new CI script
$ git push
```
You can also merge your branch into master from 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 haskell-ci regenerate.