Hello,
A lot of the things I envision for the gradual simplification of the OCaml
build and package eco-system involves using OPAM files as the pivotal package
metadata file format (Louis, I really need these x- fields for playing with
ideas…)
Since OCaml packages may also get used outside
On 13 Apr 2016, at 15:27, Daniel Bünzli wrote:
>
> Hello,
>
> A lot of the things I envision for the gradual simplification of the OCaml
> build and package eco-system involves using OPAM files as the pivotal package
> metadata file format (Louis, I really need these x- fields for playing w
Responding on list, I hope you don't mind.
Le mercredi, 13 avril 2016 à 16:35, Michael Grünewald a écrit :
> > On 13 Apr 2016, at 16:27, Daniel Bünzli > (mailto:daniel.buen...@erratique.ch)> wrote:
> >
> > 1. Where should those be installed in `lib:` (like METAs) or `etc:` (seems
> > more
Le mercredi, 13 avril 2016 à 16:31, Anil Madhavapeddy a écrit :
> Interesting idea. Do you have any specific consumers in mind for these files?
Build tool link helpers, documentation indexer, finder and viewers, etc.
> - The biggest problem I can see is that an individual OPAM file isn't much
>
> On 13 Apr 2016, at 16:46, Daniel Bünzli wrote:
>
> I think there are two problems here:
>
> 1) There's no support at the moment for such directories in OPAM install file
This is probably a rather minor problem, I guess. The presence of this support
could be used to tie-break otherwise equa
Le mercredi, 13 avril 2016 à 17:09, Michael Grünewald a écrit :
> This is probably a rather minor problem, I guess. The presence of this support
> could be used to tie-break otherwise equally good solutions but is probably
> no show-stopper.
I'm fine with your proposal, but at the moment I'm co
