[opam-devel] pin and constraints

[Louis Gesbert]

> Apparently I didn't get that pins were associated to a package version, I thought they were somehow a version for themselves, one which was greater than any other. So if I gather things correctly `opam pin PKG …` is actually a synonym for `opam pin PKG.$VERSION` where $VERSION is the latest known version of PKG.  

Not necessarily, if the package declares a version in its opam file, that will be used. Indeed, `pinned` was a version by itself in opam 1.1, but that had some quirks (in particular, version pins, or upper version constraints). It seemed more flexible and consistent to always have a version connected to the pinned package, but allow to customise that.

> You can add whatever version you want to the pin, e.g.
> 
>   opam pin add foo.1.2.3 ...

Oh yes I remember adding that now, because indeed having to use `opam pin edit` to customise the version wasn't very convenient. Thanks for reminding :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.ocaml.org/pipermail/opam-devel/attachments/20150619/ad3a14f6/attachment.sig>