Consider trying to build a custom workflow/action

[Bzomak]

Current situation

Most of the dependency building follows the same pattern: check for cache, install MSYS2 and download build dependencies, clone the repository.

Proposal

Could this be converted into a specialised workflow or action, taking all variables as required input?

Consideration: would this make things easier to modify, or more complicated, as it risks becoming its own unique build system?

[Bzomak]

Each dependency would need:

• a version/download location
• list of MSYS2 dependencies
• list of any previous dependency build jobs
• build script
• install script if appropriate

These could all be contained in a single directory.

[Bzomak]

Progress has been made in creating the individual scripts/data files.

Anotherr possible Action to consider making would be a replacement for load-dotenv, allowing to check that the file exists, and that the variable is set.

[Bzomak]

Another possible Action to consider making would be a ShellCheck action that adds the results to a nice Job Summary.