Added first run of opam-pin blog post #11
Conversation
|
Great post -- please confirm my edits. Could you also push a back reference to link the first OPAM 1.2 beta post to this? |
| <img style="float:left; padding: 5px" src="camel-pin.jpg" width="200px"></img> | ||
|
|
||
| Most package managers support some _pin_ functionality to ensure that a given | ||
| package remain at a particular version without being upgraded. |
There was a problem hiding this comment.
Just push the changes to this branch.
There was a problem hiding this comment.
https://github.com/ocaml/platform-blog/blob/master/CONTRIBUTING.md
I explicitly want to avoid multiple people trying to push changes to the same branch. We'll give each other merge conflicts, which is far more annoying.
|
I've just pushed some edits (ff11ebe). |
| pinned to a _target_, which could be a specific released version, a local filesystem | ||
| path, or a remote version-controlled repository. | ||
|
|
||
| However, the OPAM 1.1 pinning workflow only let you pin packages that _already exist_ in your OPAM |
Added first run of opam-pin blog post
|
Live at http://opam.ocaml.org/blog/opam-1-2-pin/ -- thanks for the comments! |
|
Oops, I still had some changes. Is it still worth merging ? |
|
On second thought the title might be a tad misleading "repository pinning" could be understood as "OPAM repository" :/ |
|
FWIW, it hasn't appeared in |
edit: for #6