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

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

> 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.  

This was tracked by https://github.com/ocaml/opam/issues/1799 and is released 
in opam 1.2.2, so you can do:

opam pin add name.version --dev

And yes, I agree, I think it's better to not have the version number inside the 
opam file.

MirageOS-devel mailing list



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