Ashish Agarwal

Thanks for the additional input. > some kind of master _files My goal is to eliminate _tags, mllib, odocl, etc. I know OCaml, so I want to express my build...

> a virtual abstraction of the "project tree" What can you specify with such a tree? Does it add any expressivity beyond what you can currently do, which is dependent...

Your examples dissuade me further from the overlay idea. It seems to be adding cruft on top of cruft. You'll have yet another way to specify something, making it harder...

> If I propose a single file in which to put the ocamlbuild-specific information, they may be happier. Make that file be `myocamlbuild.ml`. > I'm sure you would appreciate a...

> the `ocamlbuild -documentation` output answers your question Yes it does. Thanks. I didn't get in the habit yet of checking this.

> If someone has advice for other kind of rules to use as examples, I'm all ears. To be clear, I think the example is fine. It's just the choice...

>as I understand its only purpose is to display a graph? No, the graph operations are used in an important way. We store the dependencies between apps and libs comprising...

This feature should be easier to implement now that we have [codept](https://github.com/Octachron/codept).