David Allsopp

In the 2.2 project as I haven't yet determined if this is a regression or long-standing.

~I don't think it's too late to rename `hidden-version` - it's literally used by the compiler's beta packages only, and we haven't flipped opam 2.1 to rc. But I'll open...

Update from developer meeting: this should be spun into a full spec. It may also be possible to implement as a variable (to be used in the `available` field) rather...

(previous comments updated just to reflect that we did rename `hidden-version` to `avoid-version`, but the need for this issue remains!)

Thoughts from dev meeting to do this in 2.2: `available: if-requested` would have the benefit of being silently treated as `available: false` in opam 2.0 and 2.1 (no warning for...

The order of those in #52 wasn't a mistake - the idea was that the opam site-lib should _never_ be able to override the compiler's `META` files.

The opam packaging has been designed to work well for opam - in particular to allow OxCaml to be updated without having to rebuild all the constituent parts. The obvious...

Just as a proof-of-concept for simplifying: ```diff --- a/dune-workspace +++ b/dune-workspace @@ -2,7 +2,7 @@ (repository (name jst) - (url git+https://github.com/janestreet/opam-repository#with-extensions)) + (url git+https://github.com/dra27/opam-repository#with-extensions-dp)) (lock_dir (repositories upstream overlay jst)) ```...

> I still don't really get the point then. Regular OCaml also depends on autoconf, so in what way it isn't drop-in? Regular OCaml doesn’t ever depend on autoconf… it’d...

It’s a material concern as the number of distributions building OxCaml grows, because autoconf compatibility is not guaranteed between versions (for example, 2.71 can’t build the branches of OCaml using...