[opam-devel] Ideas from Node.js

Anil Madhavapeddy anil at recoil.org
Sat Oct 12 09:14:00 BST 2013

On 11 Oct 2013, at 23:00, Sylvain Le Gall <sylvain+ocaml at le-gall.net> wrote:

> Hello,
> This is something already somehow do-able with OASIS: just embed an
> _oasis (more rfc822 than JSON) and use oasis2opam to convert the
> _oasis to OPAM required files.
> http://oasis.forge.ocamlcore.org
> If OPAM dev would integrate a little more with OASIS (i.e. get rid of
> oasis2opam to directly read data from _oasis distributed with upstream
> package) and allow override using classic OPAM files, it will be super
> easy to release OASIS package directly in OPAM.

This has the same problem that Malcolm just explained -- you tie the 
metadata to some file *inside* the package, which requires distribution
patches if you want to override it.

What's wrong with oasis2opam that can't be fixed with a shell script
wrapper `opam-mk-oasis-package` or something similar?


More information about the opam-devel mailing list