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
[new release] lascar (0.6.0) #14827
[new release] lascar (0.6.0) #14827
Conversation
CHANGES: ## 0.6.0 (Sep, 16, 2019) * now requires ocaml >= 4.08 ## 0.6-alpha (Aug, 18, 2019) * removed dependency on camlp4 by rewriting the Fsm_expr, Fsm and ListExt parsers * dunified build and install process ## 0.5 (Apr, 9, 2018) * Library is now packed under Lascar module to prevent name clash ## 0.4 (Feb, 5, 2018) * OPAMification * Home page and documentation moved to separate web site * Added INSTALL * CHANGELOG now in .md format ## 0.3 (Dec, 14, 2017) * Added functions [map_state], [map_attr] and [map_label] * Added modules [Builtins.{Int,String,Bool}]. Rewrote some examples accordingly ## 0.2 (Nov 27, 2107) * Added [ListExt.update_assoc] ## 0.1 (Nov 6, 2107) * First public version
Yes. The package now requires ocaml >= 4.08, as specified in the |
☀️ All lint checks passed c031b69
☀️ Installability check (+1)
|
I guessing that's because you have to regenerate the opam file. I don't know how it's done but I'm pretty sure it's done by dune and not by dune-release. |
Could you also add the appropriate constraints to all the |
The opam file has been regenerated by
However,
whereas
|
It is planned. But, since |
that's what I'm saying, dune-release doesn't generate the opam file, it only adds the corresponding url field to the file but it doesn't modify anything else. Dune itself is responsible for the generation |
as for rfsm I'd rather see all the previous versions fixed before merging this PR as it could break people using it in between the merge of the two prs |
Ah ok. I understand now : |
I have no idea. |
or try |
No.
|
What do you mean by fixing all the previous versions ? |
I meant all the versions of
|
Do you mean i should open a PR for the 4.08-ready version of |
No, |
You mean, for ex, that |
Yes, only |
?? |
Deprecated yes, but it still compiles and works, nothing is different for its users. It will only require a constraint when those deprecation warnings will become proper errors in a future version of OCaml (probably in like 3 - 4 years, or something) |
Dune seems to view it as an error. E.g.:
|
Btw, the next version of |
see ocaml#14827 Signed-off-by: Marcello Seri <marcello.seri@gmail.com>
The bound on the old versions is needed independently of the new release. Recent versions of dune will fail only in dev mode, release builds will only show the warnings. For the rest, @kit-ty-kate is there any other action needed before merge? |
This is the behaviour for development purposes (i.e. when you launch |
Yes there is still a change to be made here which hasn't been pushed: #14827 (comment) (the generated opam file is not up to date) |
In your next submission be careful about the version number. The next release should be |
Ok. Shall i start the PR now or do i have to wait for this one to be completed ? |
This one should preferably be merged before. Could you push/publish the change discussed above in #14827 (comment)? |
Co-Authored-By: Kate <kit.ty.kate@disroot.org>
Done |
Thanks! |
Thanks to both of you ! |
see ocaml#14827 Signed-off-by: Marcello Seri <marcello.seri@gmail.com>
see ocaml#14827 Signed-off-by: Marcello Seri <marcello.seri@gmail.com>
A library for manipulating Labeled Transition Systems in OCaml
CHANGES:
0.6.0 (Sep, 16, 2019)
0.6-alpha (Aug, 18, 2019)
0.5 (Apr, 9, 2018)
0.4 (Feb, 5, 2018)
0.3 (Dec, 14, 2017)
0.2 (Nov 27, 2107)
0.1 (Nov 6, 2107)