Harendra Kumar

Rename the script to just packcheck?

2

We can name the scripts as: * `packcheck` * `packcheck-safe` * `packcheck-remote` or `packcheck-checkout`

Exit if PACKCHECK_GITHUB_COMMIT is not specified

2

In the CI config files, check if `PACKCHECK_GITHUB_COMMIT` is null and if not then exit, otherwise we may access an unstable URL and the build may not be reproducible.

* Add a CI for ghc-9 and add it to tested-with * Fix the description, remove cabal-v2

It does not work as of now.

run_verbose is used heavily in the script but it has a serious bug. If an argument is quoted the quotes get removed which can create problems.

This makes the sdist build slower/not incremental but it would be reliable.

Factor out the sdist git check as a separate script

1

* It can be useful to run independently, and it will be modular that way. The main script will be decluttered. * We can also allow external packcheck scripts to...

These variables are prefixed with SDIST_ but they are used for both sdist enabled/disabled cases thus causing confusion.

Have a simple CI config and generate the specific CI configs from that using a packcheck-gen-config script. We can generate configs for: * specific CI systems * for running packcheck...

`MEM_PER_JOB` would provide an idea of the memory requirement of the application under test. Based on this and the amount of memory in the system we can use: ``` $...