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

How to map versions #5

Open
fingolfin opened this issue Nov 22, 2021 · 0 comments
Open

How to map versions #5

fingolfin opened this issue Nov 22, 2021 · 0 comments

Comments

@fingolfin
Copy link
Member

For the JLLs (GAP_pkg_*_jll) the pattern is to map GAP version 1.2.3 to 100.200.300, plus potentially an offset. This decouples the GAP version from the Julia version a bit and gives us room to update the wrapper packages even if the underlying GAP packages have not changed.

  • should we adopt a similar scheme for the wrappers here in this repository?
  • how to deal with package versions like 2021.04-03 (used by Homalg and CAP these days)?
  • in the past, some packages had versions like 1.0c. I don't think that is the case for anything right now, but perhaps the GAP side should start to impose tighter constraints on version patterns?
  • GAP packages don't follow semver, so we may need to take that into account, too..
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

1 participant