the main improvement gained by having opam files everywhere is, in my opinion, that we finally have a machine-friendly way of specifying dependencies of Coq projects, so that one can locally pin a project without installing it, but install its dependencies via
opam install ... --deps-only and then check the project manually. I have spent tons of time trying to chase down unmentioned dependencies in Coq repos...
it would be great if everyone submitted both releases and their dev packages to the
extra-dev repos, but this is not going to happen anytime soon. Some people (like me) may have to make themselves into nuisances and bug people more about submitting packages. A comprehensive archive is great for many things, including new users, funding, machine learning, mining, ...
We'd definitely need automation to keep
extra-dev and the upstream repos in sync.
dune-release and/or Cyril's
packager could be adapted for this
OK, I will try to keep this in mind once I have the right name for my package.
Karl Palmskog said:
packagercould be adapted for this
packager might indeed be worth using until the Coq ecosystem has moved to Dune.
Feel free to open an issue describing what would be needed at https://github.com/coq/bot/issues/new
This topic was moved here from #Coq users > My first Coq opam package by Théo Zimmermann
Last updated: Dec 05 2023 at 04:01 UTC