Stream: Coq Platform devs & users

Topic: Merge opam patch repo to official repo

Michael Soegtrop (Oct 02 2021 at 15:25):

@Karl Palmskog : can you please have a look at (https://github.com/coq/platform/tree/main/opam/opam-coq-archive), especially extra-dev and tell me what you want to have upstream from this and if I should update the corresponding released packages of the flex packages or ask the authors (a ~flex package is identical to the one without ~flex except that version restrictions are removed from opam and possible make/configure).

Please note that there are some updates in PR (https://github.com/coq/platform/pull/148).

Théo Zimmermann (Oct 02 2021 at 16:05):

Yes, absolutely. When you discover that a package version constraints can be relaxed, please do submit the relaxing to the opam repository.

Karl Palmskog (Oct 02 2021 at 17:47):

@Michael Soegtrop it's a ton of work to compare every package, so I will try to give the general rules of thumb:

• as Théo says, modifying a package to safely relax restrictions is always welcome, either in released or extra-dev
• packages that are compatible with at least one released version of Coq should always be placed in released, even if they have more relaxed requirements than just that released Coq version

Example: coq-deriving.0.1.0~flex should be submitted to the archive as a modification of the coq-deriving.0.1.0 package in released, and definitely not live in extra-dev

Karl Palmskog (Oct 02 2021 at 17:49):

if possible, please submit "staggered" pull requests that contain at most 3 packages each. This will speed up the reviewing and merging process a lot.

Last updated: Jun 03 2023 at 05:01 UTC