On 21 Jan 2014, at 21:31, David Scott <scott.dj@xxxxxxxxx> wrote:
NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" optionally depends on "lwt & ipaddr"; some other package depends on "lwt"; but "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've misunderstood the meaning of depopts in opam. A workaround is just to install "ipaddr" first.
The intention here is to have:
- a 'mirage-types' package that is completely dependency free, and only has module type definitions with completely abstract types. - a 'mirage-types.lwt' package which specializes the above types with some concrete common defaults, specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the module signature, you now need those libraries installed to get the cmi files for them.
The OPAM line of:
depopts: [ ("lwt" & "cstruct" & "ipaddr") ]
means that if all three of the packages are present, then an optional dependency (the mirage-types.lwt) will be compiled. However, upstream users of mirage-types.lwt will thus need to explicitly depend on lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be present.
-anil
| 
