[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] Signature mismatch in tcpip 2.2.3

Le mardi, 21 avril 2015 Ã 22:24, Anil Madhavapeddy a Ãcrit :

> How is the version inferred with? Without it:
> opam pin foo git://github.com/mirage/foo (http://github.com/mirage/foo)
> ...will have the version of the latest release, I believe.  
Yes, actually I was writing:
> I'm not sure opam is at fault or can do anything here.
Mmmh actually that's only if you are assuming that a pin implies bleeding edge. 
The system I have with topkg makes pin on my packages accurately reports 
version numbers up to commit by inferring them from the VCS tags for any 
checkout, e.g. this can be seen in `ocamlfind list`. However it will indeed 
advertise itself as bleeding edge as far as *opam* is concerned.

So you are right, it seems we are missing a mecanism in the pin procedure to be 
able to communicate with which version number we would like the pin to 
advertise itself. I don't think it's a good idea to do this through the 
`version` field of the repo's opam file; that's too error prone, sync issues, 
etc. It is the VCS which has that information.  



MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.