From: Nicolas C. <war...@fr...> - 2003-02-25 03:06:33
|
> It seems to me that the priority is the shadow of the standard library. > For that, we already have a decomposition to follow, that of the > standard library itself. We need a name, a license, a compilation > strategy, and an installation strategy True, I agree to concentrate first on ExtLib and then later discuss about the OCaml web librairies repository > For the name, somebody mentioned ExtLib. For the license, the argument > has been made that we would be extending the standard library, and it > would be much simpler to keep its license. The obvious choices for the > latter two are OCamlMakefile and findlib. I'm one of the few Windows OCaml users, and findlib nor OCamlMake aren't available on this platform. I wrote a tool sometime ago called "ocamake" which is doing I think the same as OCamlMake. It's a command line tool that take several ml / mli ( and others ) files = as input, call ocamldep and then compile the whole using ocamlc or ocamlopt.= It has also an option to generate a Makefile that can be used as input for either GNU Make or Microsoft NMAKE ( no more use of two separate Makefile and Makefile.nt ). I would of course be more than happy if the ExtLib community would like t= o use this tool as a standard. It has been roughly tested and the full OCam= l sourcefile is available at http://tech.motion-twin.com . BTW, it only us= e the Unix OCaml library and don't rely on any non standard library. Perhaps I could add an XML input that well enable it to load xml project descriptors =E0 la Ant. What do you think about it ? > To proceed, I suppose we could all upload our proposals for extensions = to > the StdLib modules, and vote about the appropriateness of each one. > (I have no experience with distributed development, so I have no idea > about the actual workings of this, but the Boost's guidelines can serve > a starting point.) Please read the proposal rules I've been writting in the "Goals & Process= " thread. Nicolas Cannasse |