Hey Mindy, thanks a lot for your response :) 2016-10-24 17:20 GMT+02:00 Mindy <[email protected]>:
> There's still a ton of work to be done converting libraries (1) to topkg > and away from OASIS and (2) to use the Logs library instead of Console.log > or printf. > > I did a bit of digging[1] in the package universe, and here's a small list > of libraries that are still have an `_oasis` present in their root > directory. The `opam` package name is listed first, then the repository > where it lives: > > cstruct (https://github.com/mirage/ocaml-cstruct) > crunch (https://github.com/mirage/ocaml-crunch) > ipaddr (https://github.com/mirage/ocaml-ipaddr) > qcow-format (https://github.com/mirage/ocaml-qcow) > mirage-console-xen (https://github.com/mirage/mirage-console) (this > repository has code for both the mirage-console-xen and mirage-console-unix > packages) > > Converting things to topkg from oasis generally involves removing a bunch > of autogenerated code and adding a small amount of structure around the > invocation of topkg. topkg has documentation at > http://erratique.ch/software/topkg , including a "menagerie" of examples > at http://erratique.ch/software/topkg/doc/Topkg.html#menagerie . It's > helpful to know a small amount about ocamlbuild (the build system that > _oasis was autogenerating code to manage, and which topkg provides a > simpler interface to) -- some documentation is available at > https://nicolaspouillard.fr/ocamlbuild/ocamlbuild-user-guide.html . > > This is really helpful, I'll start reading about the two packagers. Is this [1] a good example of the changes needed for the transition? Also, I guess that after making the modifications I should be able to generate the package and maybe install it locally but, are there any additional checks/testing in order to be sure that all went fine? > Logging's just seen a lot of activity over the past weekend! Probably > verbosemode and hannesm can speak more to what might be valuable to look at > immediately. > > Similarly, I think djs55 can speak better to what might make sense to look > at alongside the "tiny vm for load testing" project. > > Ok, thx for the pointers, I'll try to continue with them after I get my feet wet with topkg :) > Thanks a lot for reaching out to the list! We're happy to hear from you. > :) > > Thank you :) [1] https://github.com/mirage/mirage-bootvar-xen/commit/bfee b6cfb7851177eeba48c863bd2b56d381d1ac
_______________________________________________ MirageOS-devel mailing list [email protected] https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
