Closed gildor478 closed 7 years ago
The dev version of oasis2opam
generates:
depends: [
"base-unix"
"camlp4" {test}
"expect" {test & >= "0.0.4"}
"fileutils" {test & >= "0.4.2"}
"ocamlbuild"
"ocamlfind" {>= "1.3.1"}
"ocamlify" {build}
"ocamlmod" {build & test}
"omake" {test}
"ounit" {test & >= "2.0.0"}
"pcre" {test}
]
depopts: [
"benchmark"
]
conflicts: [
"benchmark" {< "1.2"}
"oasis-mirage" {= "0.3.0"}
"oasis-mirage" {= "0.3.0a"}
]
Notice that oasis2opam
issue warnings on https://forge.ocamlcore.org/frs/download.php/1669/oasis-0.4.8.tar.gz about oasis.install
and _oasis_remove_.ml
. It would be good to add those files to the tarball.
It seems build & test
is causing a problem, not implying build
(even though the manual seem to say so).
_oasis_remove_.ml was the thing used to "chdir" ? If this is the case, it should not be useful anymore and it would be better to remove it.
Concerning the the oasis.install, I thought it belonged to the packaging and should be in opam/files (I read it in the manual). Why would the upstream author have to provide this file?
About _oasis_remove_.ml
, good to know that the -C
flag is available in the latest release. I've updated oasis2opam
and the PR for oasis.
For oasis.install, the OPAM manual indeed talks about that file without expressing a clear preference. A discussion — somewhere on Github I think — made clear however that <pkg>.install
files are not welcome in the opam-repository in order not to "pollute" everybody with extra files that may not be useful for them.
Forking the discussion in #30 and #31 so that we can close this bug.
See https://github.com/ocaml/opam-repository/pull/8031
I have the following in my _oasis:
The generated opam:
And the following error when building:
What I expect is to have either: