2022 Developer Meetings

• 2022.01.21
• 2022.01.14
• 2022.01.07

21-Jan-2022

Agenda

• @NathanReb: Downloading and caching opam repositories
• @dra27: opam-dev team visibility, MAINTAINERS, etc.
• @dra27: who goes in AUTHORS!
• @dra27: opam-depext release needed for 5.00.0 compatibility (see the horror of ocaml-opam/opam-depext#147

New issues

• #4994
• #5010
• #5011
• #5012
• #5013

14-Jan-2022

Agenda

Towards a 2.2 release plan

Sweep through these issues (and others in the "Bump to 2.3?" project column, as necessary)

• #4518, #4519, #4520, #4521 (deprecated fields - this was gated on there being a visible format upgrade in opam 2.2)
• #4543 (non-recursive --with-test / --with-doc in opam list)
• #4727 - status?
• #4649 - status?
• #4686 (linting on pinning) - status? previous discussion?
• #4419 and #4207 - status?
• #4311 - status?
• #4272 - status?
• #4541 - status?
• #3722 - status?
• #4762 - status?
• #4890 - status?
• #4959 - someone happy to implement?

New issues

• #4992 - opam root message in opam init
• #4991 - doas support (esp. for Alpine)

7-Jan-2022

Agenda

New Issues

• #4977 - opam pin add <archive url> should read package descriptions from archive
• #4984 - tracking git branches following opam switch create .
• #4985 - permit opam switch export --freeze with path pins (adding --force, --permissive or something)

Notes added on issues

Last week

• Louis / Raja / Kate code walk-through of the solver
• Kate: following this, deep into a rabbit hole looking at the empty conflict resolutions. Looking at pulling in 0install's conflict resolution solver instead.
• Raja: updated software heritage PRs - fallback mechanism should be ready later today. Had another look at #4967: several issues are masked by E3 ("format error") where the actual error is then just displayed as a string. Can look at propagating the precise error from OpamFile. For opam repo set-url, implemented the restoring of the backup if the new URL fails. Worked on tests for lock file / rec-pin (which are strangely intertwined!). Spotted that opam upgrade completely ignores lock files - branch in progress to fix that.
• Louis: adding some (more) tests. Finally merged opam pin --current and the refactoring (#4973 and #4969) and so coming back to opam install --formula (#4975). Been looking at the issues discussed at the previous meeting with the --deps-only issues - various solutions explored - arrived at a working branch which needs cleaning up and then PR opening
• David: deployment of glibc 2.34 opam-repository patches should be finalised for next week; MSVC patches are now merged upstream and deployed to Docker images (so our CI can adopt them as well)