-
Notifications
You must be signed in to change notification settings - Fork 30
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
Higher version number #1
Comments
Or 4.09.0, for that matter 🙂 |
That seems fine to me. Thinking about it again, we should probably not make this package available for OCaml < 4.09, otherwise there will be a conflict for the ownership of file |
Indeed - but once that opam-repository PR is sorted, the package becomes uniformly installable with |
It's just that we have a problem if we install things in this order:
in this case, ocaml will install It feels safer to simply wait for 4.09 and release this repo with a |
I agree - all I meant was to release with a version number that's definitely bigger than the graphics.4.08.0 which will hopefully by then be in opam-repository. |
The opam-repository PR is merged. As it happens, you can build later versions of graphics with older compilers (I seem to remember finding that OCaml 3.07 could actually compile the 4.06.0 graphics library!) but for opam-repository I elected to have it that you always get the version of graphics which matches the compiler, just for the "least surprise" principle. So when 4.08.0 is released, I'll do an update on opam-repository for graphics.4.08.0 and then when 4.09.0 comes out we can release this package as graphics.4.09.0 with the an |
That works for me! |
I updated the changelog to be sure to use the right number when release time comes |
The latest release is numbered 5.0.0, so I guess this report served its purpose and can be closed now. |
Note ocaml/opam-repository#12674 which is blocked only by a CI issue and once that's fixed will be wanted. Can we pick a higher initial release number - is there anything prevent 5.0?
The text was updated successfully, but these errors were encountered: