-
Notifications
You must be signed in to change notification settings - Fork 22
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
port to dune, upgrade opam metadata and remove unused code #14
Conversation
avsm
commented
Feb 2, 2019
•
edited
edited
- removed vestigial ocamlbuild files (_tags)
- port to dune (as dune 1.7 will issue jbuild deprecation warnings)
- upgrade opam metadata to the 2.0 format
- remove ocaml <4.01 support, as minimum version is now ocaml 4.02+
- restore -inline 1000 to build rules (dropped with jbuilder port)
- update travis to test with 4.07->4.02 inclusive
- removed vestigial ocamlbuild files (_tags) - port to dune (as dune 1.7 will issue jbuild deprecation warnings) - upgrade opam metadata to the 2.0 format - remove ocaml <4.01 support, as minimum version is now ocaml 4.02+ - restore -inline 1000 to build rules (dropped with jbuilder port)
And thanks to @rgrinberg, the mystery of the failing tests is resolved -- it needs to be built in release mode as dev mode includes |
|
.travis.yml
Outdated
@@ -4,12 +4,12 @@ install: wget https://raw.githubusercontent.com/ocaml/ocaml-ci-scripts/master/.t | |||
script: bash -ex .travis-opam.sh | |||
env: | |||
- OCAML_VERSION=latest TESTS=true PACKAGE=ocplib-endian |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line should be removed since ocaml-ci-scripts removed the support for "latest" version.
Can this be merged and released, please? (especially the jbuilder -> dune migration part) |
I hand merged it. I didn't take the bigarray-compat part to avoid increasing the minimal ocaml version for lwt to 4.03. I will wait for #20 to be resolved to release. I'm curious @glondu why do you care about this ? Can't debian stick to the currently released version ? There is no difference between this one and the tarball except the build system. |
Yes, Debian can stick to the currently released version (1.0). When I wrote my comment, I thought that version was using jbuilder (which is not the case), and I want to get rid of jbuilder in Debian. |