Re: version pinning in OPAM

[Thomas Gazagnaire <thomas.gazagnaire@xxxxxxxxx>]

I've pushed a first version of pinning support to my OPAM fork: 
https://github.com/samoht/opam.git

$ opam pin mirage 0.3dev                      # pin mirage to version 0.3dev
$ opam pin mirage /path/to/mirage       # pin mirage to the content of 
/path/to/mirage
[cd /path/to/mirage && hack hack hack]
$ opam update && opam upgrade
$ opam pin mirage none

I've done a limited amount of testing, and I'll integrate it upstream when it 
works sufficiently enough to be used with mirage.

I'll work on the upgrade to be able to upgrade just a collection of packages 
instead of doing a full upgrade.

--
Thomas

On Jul 11, 2012, at 12:39 PM, Anil Madhavapeddy wrote:

> On 11 Jul 2012, at 11:11, Thomas Gazagnaire wrote:
> 
>> 
>>>> Is this convenient ? Would it be better to have "opam pin mirage 
>>>> /local/path" instead (ie. no package version) and a more specific 
>>>> update/upgrade command (like "opam pin -reinstall") to just upgrade the 
>>>> pinned packages without having to do a full upgrade ?
>>> 
>>> The only problem I see with 'update && upgrade' is that you are forced to 
>>> upgrade all packages, including any other ones that came from upstream.  
>>> Not sure if that will be a problem in practise or not.
>> 
>> Yes that's exactly the problem with update/upgrade. Any better idea ? 'opam 
>> pin -update' to update/rebuild only the pinned packages in one step ?
> 
> This seems to be independent of the pinning support.  Why not allow 'opam 
> update && opam upgrade lwt' to only update that package (and its dependents 
> that must be recompiled due to the new interface)?
> 
> -anil