[opam-devel] current opam-repository policy : who can modify a package description

Hannes Mehnert hannes at mehnert.org
Mon Feb 22 16:52:45 GMT 2016

On 02/22/16 05:43 PM, Anil Madhavapeddy wrote:
> I mean that there are hundreds of OCaml packages that existed
> before OPAM that have their own versioning conventions (most of
> which are not semantically versioned), and these are directly
> mapped into OPAM package versions.
> It would be incredibly useful to have an enforcement of semantic
> versioning, but at this stage in the current repository would
> require a mass remapping of upstream versions into the scheme.

My idea would be to leave the versions which are there in place (since
the constraints are already setup), but for new releases require that if
the API changes the major version be (at least) last-release.major + 1.

No remapping needed; in case such pre-opam packages want to do new
releases, they should conform to semantic versioning.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ocaml.org/pipermail/opam-devel/attachments/20160222/19bdddf0/attachment.sig>

More information about the opam-devel mailing list