rocq 9.0.0 (renamed formula)
- [ ] Have you followed the guidelines for contributing?
- [ ] Have you ensured that your commits follow the commit style guide?
- [ ] Have you checked that there aren't other open pull requests for the same formula update/change?
- [ ] Have you built your formula locally with
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where<formula>is the name of the formula you're submitting? - [ ] Is your test running fine
brew test <formula>, where<formula>is the name of the formula you're submitting? - [ ] Does your build pass
brew audit --strict <formula>(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it passbrew audit --new <formula>?
Sorry for creating this PR, #216253 just stopped (and there are no any updates from @cho-m), I just wanted to move it further
it looks like math-comp 2.4.0 requires newer ocaml
https://github.com/Homebrew/homebrew-core/pull/204847
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
in progress
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
.
@botantony Can you rebase this into the origin/main branch? Let's check the most recent build status.
There is a coqc but the command failed.
/opt/homebrew/opt/rocq/bin/coqc --print-version failed with exit code 2.
In previous PR, I was originally trying to figure out a better solution to the ML files as the current requirement of using an environment variable isn't ideal.
Sadly I haven't found a great way as we don't want to create formulae for each opam package (against our policy and a maintenance headache).
May just keep current approach to avoid blocking OCaml update
:shipit: @fxcoudert has requested bottles to be published to this PR.
[!CAUTION] Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.