>> Any solution to pinned packages + config.ml <http://config.ml/>? Is there >> some basic reading I should do? > > I'm afraid we don't really have solutions for this yet. The closer you could > get would be to create your own opam-repo and put in there the dev packages > that you need. See what we do for mirage for instance: > https://github.com/mirage/mirage-dev <https://github.com/mirage/mirage-dev> Or maybe put your pin commands in the `Makefile.user`? That's an interesting request actually, as it points out that the library/package/opam stuff is not totally sorted out yet (cf discussions early) We could have a more declarative APIs for this kind of dependencies. Something like:
val pkg: name:string -> ?url:string -> libs:string list val foreign: ... ~pkgs:pkg list -> ... I'll think about that a bit more. Thomas >> On Sun, Feb 21, 2016 at 1:00 PM, Sean Grove <[email protected] >> <mailto:[email protected]>> wrote: >> Great, thanks for that. I actually need to pin a bunch of packages (e.g. >> https://github.com/mirage/mirage-bootvar-xen/issues/15 >> <https://github.com/mirage/mirage-bootvar-xen/issues/15>) to get the >> unkernel booting appropriately, but I don’t see how to specify that in >> config.ml <http://config.ml/> - I’m just listing package names, and so I >> suspect that someone else trying out the project will run into issues with >> the wrong version of the package - what's the solution here? >> >> On Sun, Feb 21, 2016 at 8:38 AM, Richard Mortier >> <[email protected] <mailto:[email protected]>> wrote: >> On 21 February 2016 at 15:53, Thomas Gazagnaire <[email protected] >> <mailto:[email protected]>> wrote: >> >> foreign >> >> ~packages:[ >> >> "irmin", ["irmin.mem"]; >> >> "tls", ["tls.mirage"]; >> >> ] >> >> "Unikernel.Main" ... >> >> >> >> Then it's obvious which OPAM package provides each library and it's >> >> harder for them to get out of sync. >> > >> > That's a good idea. Could even be an optional argument as most of the time >> > the opam package and findlib library have the same names. >> > >> >> Hm. Several libraries have multiple parts though. >> >> Also are we going to make it clear that we're mandating only libraries >> expressed as OPAM packages can be used with Mirage? >> >> (I like the idea of making the link between the package and the >> library clearer in the common case though.) >> >> -- >> Richard Mortier >> [email protected] <mailto:[email protected]> >> >> _______________________________________________ >> MirageOS-devel mailing list >> [email protected] >> <mailto:[email protected]> >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> <http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel> >> >> >> _______________________________________________ >> MirageOS-devel mailing list >> [email protected] >> <mailto:[email protected]> >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >
_______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
