oasis2opam.0.6.1 - via opam-publish

[Chris00]

Tool to convert OASIS metadata to OPAM package descriptions
Generate OPAM files from _oasis. Most of the metadata supported by
oasis is translated to OPAM. A simple .install file is written to
handle executables (until oasis supports the functionality itself).

---

• Homepage: https://github.com/ocaml/oasis2opam
• Source repo: https://github.com/ocaml/oasis2opam.git
• Bug tracker: https://github.com/ocaml/oasis2opam/issues

---

Pull-request generated by opam-publish v0.2.1

[camelus]

✅ All lint checks passed bdef4ba

• These packages passed lint tests: oasis2opam.0.6.1

---

✅ Installability check (3718 → 3719)

• new installable packages (1): oasis2opam.0.6.1

[dbuenzli]

A simple .install file is written to
handle executables (until oasis supports the functionality itself).

What does this do exactly ? It seems to me that oasis already supports the installation of executables.

[Chris00]

On Tue, 21 Jul 2015 02:51:19 -0700, Daniel Bünzli wrote:

| A simple .install file is written to
| handle executables (until oasis supports the functionality itself).

What does this do exactly ? It seems to me that oasis already supports the installation of executables.

But not their removal, unless the initial setup.data is present.

[dbuenzli]

But not their removal, unless the initial setup.data is present.

But you should not use .install files if the package installs the file itself. .install files are to let opam do the install. If you generate this statically it will lead to problems on windows see ocaml/opam#2253

[Chris00]

On Tue, 21 Jul 2015 02:58:47 -0700, Daniel Bünzli wrote:

| But not their removal, unless the initial setup.data is present.

But you should not use .install files if the package installs the file itself. .install files are to let opam do the install. If you generate this statically it will lead to problems on windows see ocaml/opam#2253

I agree that these files should be generated by oasis — that's the meaning of “until oasis supports the functionality itself”. If only I got the time...

[dbuenzli]

I agree that these files should be generated by oasis — that's the meaning of “until oasis supports the functionality itself”. If only I got the time...

They should be generated only if oasis doesn't perform the install itself and please don't do that meanwhile with oasis2opam, it will break any oasis package using oasis2opam on windows for no good reason.

[Chris00]

I will release a version that uses oasis generated setup.* to do the install and removal.