Re: opam-repo-dev now less useful

[Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx>]

On 11 Feb 2013, at 10:24, Anil Madhavapeddy wrote:

> On 11 Feb 2013, at 10:01, Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx> 
> wrote:
> 
>> not sure how useful that would be - surely if i want the dev version, i'm 
>> doing some dev on it, which means i've got the source somewhere. better to 
>> have an easy way to have opam manage installation of locally constructed 
>> packages? (which i think is what pin is isn't it?)
> 
> Indeed, I don't quite understand the use-case of dev vs pin here.
> 
> A simpler solution might be just to have a 'head' field in the url file, 
> which contains the URL for the latest revision (e.g. 
> git://github.com/mirage/mirage-platform).  Then `opam pin mirage` could 
> default to the dev revision if no other path is specified.
> 
> Doesn't seem like the most important feature though. As Mort notes, most 
> people will want to clone the source locally to modify it.
> 
> Actually, a commonly requested feature is 'opam source' to retrieve the 
> package archive.  So this feature could work well with that.
> 
> $ opam source mirage.0.7.2
> or
> $ opam source mirage --head
> <clones into mirage.HEAD>
> followed by
> $ opam pin mirage mirage.HEAD


that's probably handy. also useful to be able to easily pull source for 
some/all the dependencies of a package when setting up to try and do some 
development. maybe just an easy way to output all the deps and their source 
urls?  (just in case, e.g., it turns out i already have those trees -- seems 
that letting opam start to magically manage my dev environment might be a step 
too far... :)

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may 
contain confidential information. If you have received this message in error, 
please send it back to me, and immediately delete it.   Please do not use, copy 
or disclose the information contained in this message or in any attachment.  
Any views or opinions expressed by the author of this email do not necessarily 
reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.