Build dependencies as well?

[fingolfin]

Right now this only builds the package being tested.

But what if its (recursive) dependencies also need to be built? E.g. if a package depends on orb and datastructures then at least those two should also be built, no?

[wilfwilson]

I was about to comment "you can just do this with the GAP_PKGS_TO_BUILD" input to gap-actions/setup-gap, but I see that this has now been removed in @v3 of that action.

[stertooy]

I have some questions/concerns on this:

1. Do we only build dependencies shipped with GAP, or also dependencies installed later in the workflow?
2. How do we ensure that we only build those versions of the dependencies actually needed? E.g. if a dependency has version v1 shipped with GAP, but later in the workflow version v2 is downloaded, we don't want to build v1.
3. Do we want to do this recursively?

[fingolfin]

All good questions and I don't have good answers right now, just more concerns: if we install GAP package dependencies; then we also should perhaps install their distro dependencies via apt install / brew install -- e.g. singular for Singular, or libcurl-dev (or so) for CurlInterface). Basically the data store in https://github.com/gap-system/PackageDistro/blob/main/tools/gather_dependencies.py

Relevant discussion: gap-system/PackageDistro#1211