Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GAP 4.9 syntax used, but PackageInfo.g claims 4.7 support #27

Closed
jamesjer opened this issue Apr 28, 2018 · 2 comments
Closed

GAP 4.9 syntax used, but PackageInfo.g claims 4.7 support #27

jamesjer opened this issue Apr 28, 2018 · 2 comments

Comments

@jamesjer
Copy link

Attempting to use polycyclic 2.13.1 with GAP 4.8.10:

Loading the library and packages ...
Syntax error: literal expected in /builddir/build/BUILDROOT/gap-pkg-polycyclic-2.13.1-1.fc29.x86_64/usr/lib/gap/pkg/polycyclic-2.13.1/gap/exam/generic.gi line 89
pairs := ListX([1..n-1], i -> [1..n-i], {i,j} -> [j, i+j]);
^
The Dependencies section in PackageInfo.g says GAP := ">= 4.7". That should either be updated to 4.9, or the old function syntax should be used.

@olexandr-konovalov
Copy link
Member

@jamesjer thank you. We hope to have GAP 4.9.1 very shortly (basically as soon as gap-system/gap#2418 completed and merged) and new Polycyclic will be usable.

On a meta level, dependencies in GAP packages IMHO are very unreliable in claiming backwards compatibility with old GAP releases. While some packages may have actually try to maintain it and have different provisions for different versions of GAP, some may still state some 5 or more years old releases and I don't expect that each change in such packages is really tested with old GAP releases. I think going back beyond one major release is completely impractical. In my packages, I am trying to bump GAP version number periodically, to reflect the version of the system under which it has been tested.

@fingolfin
Copy link
Member

Thanks for your report, this will be fixed in the next release.

fingolfin added a commit that referenced this issue May 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants