I’m thinking of making a change that might affect a ton of opam packages, and rather than submit the change and have it ripple thru the OPAM-CI, I thought: is there a way I could build on my own machine with the change, and systematically build -everything- ? I know that it’s possible to reproduce OPAM-CI on individual packages (by cut-and-paste from the error-report!!) which is what got me to thinking: there must be a way to do this more-pervasive install …
1 Like
This sounds like a use case for https://github.com/ocurrent/opam-health-check (this is what powers http://check.ocamllabs.io)
2 Likes