-
Notifications
You must be signed in to change notification settings - Fork 32
Description
Not an issue, more a progress report
When this preparation is done, this issue could be kept open for later reference, but the similar issur for coq-8.16 should be closed.
As a first step, I prepared my own environment by creating an opam switch containing coq-8.17rc1
opam switch create coq-8.17rc1 ocaml-base-compiler.4.13.1
eval $(opam env)
opam repo add coq-released https://coq.inria.fr/opam/released
opam repo add coq-core-dev https://coq.inria.fr/opam/core-dev
opam update
opam install coq.8.17+rc1I cloned coq-dpdgraph and looked at the commits that had gone into coq-v8.16, trying to reproduce them intelligently. I also cloned the repository templates from coq-community
I modified by hand the files meta.yml and configure.ac, (Important : only these two files are modifled by hand), then I ran templates/generate.sh, this generated modifications for a collection of files: coq-dpdgraph.opam README.md .github/workflows/docker-actions.yml
Then I ran autoconf it complained about a bad usage of AC_OUTPUT (but only as a warning)
Then ./configure showed that I had not install ocamlgraph in my opam switch.
Then make make test and make distrib
The make test command exhibited a few warnings that need to be fixed in coq-master, probably. I am spending some time trying to fix these warnings, but in the main branch.
Normally, after the make distrib, I should have an archive of the code that can be used for opam.
All the modification were committed on a branch coq-v8.17 which was pushed on the coq-community repository.
Then an opam file was prepared in the opam-coq-archive, this file was place in the released set of packages, but it is of course easy to move it to another repository while waiting for coq 8.17 to be released.