Hello, On 02-06-2011, Daniel Bünzli <[email protected]> wrote: > Hello Sylvain, > > I didn't get your answer (please keep me on the cc). > >> As far as oasis and uuidm is concerned, the migration to oasis is quite >> simple. I already crafted a tool to manage oasis package in debian >> (oasis2debian: > > So packagers only need an _oasis file describing the library and voilà ? > > The situation now is that I have an ad-hoc build script which has > various targets to build and install the libraries. My plan is to > remove these scripts from the distributions and replace them by an > _oasis file. Is that all what you need ? >
Well, there are two parts: 1 - _oasis describes build dependencies, from this file a tool like oasis2debian can deduce build dependencies and what documentation is built 2 - setup.ml, generated from _oasis using "oasis setup", is a standard entry point in the build system. But all this remains helpers to write a debian packages from _oasis, the tool is still in development and IHMO a Debian packager will still need to review by hand the changes made by the tool. But I think, it is safe enough to say that _oasis + setup.ml is enough to have a good package. BTW, you can keep you custom scripts and call them through oasis using "BuildType: custom" "XCustomBuild: myscript.sh". Cheers, Sylvain Le Gall -- My company: http://www.ocamlcore.com Linkedin: http://fr.linkedin.com/in/sylvainlegall -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
