Open fingolfin opened 3 years ago
Note this:
gap> GAPInfo.Version;
"4.11.1"
gap> GAPInfo.Version:="4.10.1";
"4.10.1"
gap> GAPInfo.Version;
"4.10.1"
Doing this shouldn't be too hard either:
GAPBRANCH
, say version
X.Y
or X.Y.Z
for themversion: X.Y
) is automatically mapped to version: X.Y.Z
the version of the latest release of the X.Y
release series
version: latest
would use the latest stable releaseversion: BRANCHNAME
to test against that GAP branch
stable-*
and master
for nowORG/REPO#branch
to permit using a branch from an arbitrary GAP forkClone GAP
step then is changed to say Get GAP sources
and we download GAP from the appropriate place (i.e., for all new enough releases from https://github.com/gap-system/gap/releases/download/vX.Y.Z/gap-X.Y.Z.tar.gz -- actually, we could retroactively provide these for 4.9.x and 4.10.x, too (I don't think it makes sense to try to support older GAP versions for this)That should be most of it.
Of course if we were to switch to docker images (see also issue #16) this may become moot, but unless someone actively works on that, I don't see why we shouldn't try the above (or a variation thereof)
Right now, we install GAP always from git; to test against e.g. 4.10, we use the stable-4.10 branch.
But it would be useful to (also?) be able to test against actual releases, such as 4.10.2 or 4.9.3. One important difference is that
GAPInfo.Version
is set correctly there (in git build, it is always4.dev
or something like that, which means version checks in code don't work).Ideally, the user would be able to either specify "4.10" (and then gets whatever the latest 4.10.x is) or even a specific version like "4.10.2" (however, this later point is less important).