Louis Gesbert

woohoo issue #5000 ! :tada:

Thanks for reporting. Bash init is a mess ;) The solutions often seems simple, but the practice always shows different... E.g. initially we had been using `.bash_profile`, but just creating...

From experience, although it's counter-intuitive, you generally lose more information by separating stderr and stdout ; the reason being that relative ordering generally matters, and is in many cases a...

This is different from `libraries` and `syntax` in that, although unused, it is documented and doesn't do absolutely nothing. I'd say we can keep it (with the experimental flag) until...

See my comment on https://github.com/ocaml/opam-repository/issues/14185. In your example above, a downgrade of dune won't be allowed (although they appear in the same formula, the `{build}` tag and the version constraint...

> The safest way to interpret it is: if X is a build only dependency, then the build artifacts will be exactly the same no matter the version of X....

For reference, the original discussion for the feature is in #1231

Sounds good, and thanks for suggesting this. I would really like it if the new operator was defined on any allowed version, rather than throwing errors: this needs some generalisations...

Sounds more intuitive, indeed. The definition for `next(v)` could be rephrased accordingly: > `next(v)` is the version `v` with the "compatibility version number" incremented, and everything after it stripped. >...

> I suggest, at least, requiring a semver version to appear at the beginning of the package version I am not so sure: for example, JS recently moved to have...