Switch to jbuilder

[djs55]

This is a duplicate of #29 from @nojb , rebased to fix the conflict.

[nojb]

I just remembered something - strictly speaking the jbuilder build is not backwards-compatible because it defines a single sha ocamlfind package, as opposed as the hand-written Makefile which defined sha.sha1, sha.sha256, sha.sha512 IIRC.

Should we do something about it?

[djs55]

I think it's possible to add extra (dummy) ocamlfind subpackages using a template META file. I'll take a look. Also it will be interesting to see the revdeps on opam-repository for the 1.12 I just released (maybe they'll all be broken?)

…

On 2 Jan 2018 21:30, "Nicolás Ojeda Bär" ***@***.***> wrote: I just remembered something - strictly speaking the jbuilder build is not backwards-compatible because it defines a single sha ocamlfind package, as opposed as the hand-written Makefile which defined sha.sha1, sha.sha256, sha.sha512 IIRC. Should we do something about it? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMHukx05DUXJBRpYjDNeruw7ejby9efks5tGp_pgaJpZM4RRDIr> .

[nojb]

I do not think it is worth the trouble. I took a quick look at the reverse dependencies of sha and there is only one (vhd-tool.0.12.0) that refers to the now-non-existent package sha.sha1. All the rest refer to the top-level package sha which works fine with the jbuilder setup. I don't find the idea of adding dummy (empty) ocamlfind packages very appealing.