David Allsopp

> I think there's an easy compromise, though - instead of `os != "win32"`, if it's `os != "win32" | os-distribution = "cygwinports"` then the packages remain installable when using...

@jonahbeckford - which bit of the #windows-support thread on Discord are you referring to? (sorry, I don't use Discord very frequently, and I'm struggling to find the context). On the...

@MSoegtropIMC - `os-distribution` refers to opam, which I believe you're using from "OCaml from Windows". I just kicked off a build of Coq Platform "from sources" and `opam var os-distribution`...

Agreed - let's remember to bring this up when 5.1 is branched in April (it might be worth having a post-messages for the releases regardless, even if it doesn't need...

The next release of the num library should address this (as it generates a `num.install` instead of using the `install` command)

> Perhaps we should just let packages mark if they are incompatible with dune caching inside the dune project itself? That doesn't work for existing releases, though. However, the other...

I will try to do something about the script in the coming days and then we could merge this as a trial.

@MisterDA has been doing some work around this which may help. Otherwise, I agree adding `-Wnodeprecated-non-prototype` would be good, but I would do this specifically for `runtime/interp.c` rather than for...

We should have a look at what @MisterDA has been putting together (which was still done using `sed`). However, another option - especially if we're generating a "nicer" prims.c -...

@edwintorok - just to clarify, is the problem building the 5.0 dev branch (where `-Werror` is on by default) or building a release tarball/opam switch (where warnings should definitely not...