Thomas Gazagnaire

I guess this is expected: a1c715160e91fc7e3d8880bb987087c069a3fa11 seems to indicate that directory targets cannot contain generated sources. Do you think this restriction could be lifted?

I'm fine having a script which expands the includes. But you can at least generate an entry page per package and per modules in that package (which seems a more...

I don't think the "submodule/..." is very useful in practice. But having a direct links to package/ and package/module would be very useful.

To be more complete on the uri scheme. It would be nice if opam-doc generates overlay on top of an existing repository (as we plan to do in `opam2web`). eg....

Yes, the plan is to switch to `packages/name/name.version/` once the final 1.1 is out. Regarding the "long" names, OPAM is looking for any files called `packages/XX/YY/ZZ/name.version/opam` to compute the available...

The way to make this happen is to add a new field in `opam` of `dune-project` to be able to specify what upstream repository to use. This way that will...

The list of repositories is not very dense - it would be nice to pack more information in these instead of having to scroll. Maybe use multiple columns or removing...

Thanks for the improvements so far. But I still find the font quite big (at least on my laptop screen), so I'm using an 80% zoom to see more info...

> You can't git bisect if older commits no longer know which commit they build against. That's also the case if you also update your dependencies, as you will need...

Yes indeed, sometimes the changes are on purposes. So probably an allowed failure would be enough (e.g. if the check fails, do not fail the whole build) -- but it's...