-
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
build with dune #31
base: master
Are you sure you want to change the base?
build with dune #31
Conversation
Not sure if an |
|
@olafhering this is an invalid opam package, leading your opam file to be invalid, it should be |
Signed-off-by: Olaf Hering <olaf@aepfle.de>
Signed-off-by: Olaf Hering <olaf@aepfle.de>
Signed-off-by: Olaf Hering <olaf@aepfle.de>
I'm not convinced that there is any benefit to switching Camlzip to Dune. Maybe you could enlighten me? At any rate, the two ocamlfind package names "zip" and "camlzip" are here to stay. |
Mature packages that doesn't change much have less incentive to move to dune, and adding problems because of the transition would be sad, but:
To reduce breaking changes:
|
The main benefit that I see is having the wrapper, currently camlzip fails to build with zlib. |
I'm not aware of this issue. Can you elaborate? |
@xavierleroy module name conflict, camlzip has a module called zlib, zlib is a library called zlib, so it will fail at link time because camlzip is not wrapped. Of course making it wrapped is also a breaking change on the API but we can have both for now, wrapped and non wrapped. |
I recently worked on an update of this port for The port is available here: https://github.com/dune-universe/camlzip/tree/dune-universe-v1.11. |
For the deprecated names, neither deprecated-library-names and deprecated_package_names were satisfying? |
I didn't use these features because the It also seems that @xavierleroy has no intention to deprecate either library names. If the maintainers wish to switch to dune, I'm more than happy to open a PR and adapt it however they see fit, including deprecating one of the lib name or wrapping the library to avoid modules clashes! |
also make use of stdlib-shims, but this is of course optional IMHO.