Open Chris00 opened 9 years ago
Your OPAM package depends on oasis. I do not think it is necessary. Maybe you want to give a try to oasis2opam?
To the first question, I had no particular reason for not choosing development mode so I'll give it a try. To the second, oasis2opam wasn't released when I first started development and I haven't had time to switch to it yet. Happy to accept changes ;)
For oasis2opam
nothing has to be changed. In the directory packages/
of an OPAM-repository checkout, issue oasis2opam URL_of_your_tarball
and the OPAM files will be created (just make sure that _oasis
— and _opam
if any exists — are present in the tarball).
Why not use oasis dynamic mode for development¹ instead of commiting again and again the generated files (
setup.ml
,_tags
,myocamlbuild.ml
...)¹ Not for the final tarball for OPAM which then will be uploaded and associated to a Git tag instead of being the content of the Git tree.