From: Vincent Aravantinos <vincent.aravantinos@yahoo.fr>
To: Gurus Ocaml <caml-list@inria.fr>
Subject: Re: Cherry-picking modules (was Re: [Caml-list] [ANN] OCaml Reins 0.1 - Persistent Data Structure Library)
Date: Wed, 26 Sep 2007 17:50:15 +0200 [thread overview]
Message-ID: <6229FB62-3630-449C-BDDC-AD18FAB05DAE@yahoo.fr> (raw)
In-Reply-To: <Pine.GSO.4.64.0709261109010.10669@loompa>
Ok, there is camlget, ok there is ocamlfind, ok there is godi.
Maybe if there were some 'Inria'-made tool (seems camlget is starting
point for that ?) that be settled in the standard ocaml distribution
would help to make everyone agreed, don't you think ? This does not
solve intrinsic problems such as "I prefer dynamically linked" vs "I
prefer statically linked" but at least that would be a tool everyone
could rely on. Then everyone is free to use it or not. It would even
simplify the task for library-writers.
BTW isn't it the same with ocamlbuild ? Before there were Omake and
others. Now it seems to settle some kind of standard.
My 2cents.
Vincent
next prev parent reply other threads:[~2007-09-26 15:50 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 18:53 [ANN] OCaml Reins 0.1 - Persistent Data Structure Library Mike Furr
2007-09-25 19:14 ` [Caml-list] " Daniel Bünzli
2007-09-25 19:30 ` Mike Furr
2007-09-25 22:16 ` Cherry-picking modules (was Re: [Caml-list] [ANN] OCaml Reins 0.1 - Persistent Data Structure Library) Daniel Bünzli
2007-09-25 23:33 ` Cherry-picking modules (was " Sylvain Le Gall
2007-09-26 6:41 ` [Caml-list] " skaller
2007-09-26 7:22 ` Daniel Bünzli
2007-09-26 8:19 ` skaller
2007-09-26 8:30 ` Daniel Bünzli
2007-09-26 8:58 ` skaller
2007-09-26 9:49 ` Daniel Bünzli
2007-09-26 10:26 ` Sylvain Le Gall
2007-09-26 11:45 ` [Caml-list] " Jim Miller
2007-09-26 12:37 ` Sylvain Le Gall
2007-09-27 10:11 ` [Caml-list] " Richard Jones
2007-09-26 12:22 ` Daniel Bünzli
2007-09-26 12:58 ` skaller
2007-09-26 16:47 ` Sylvain Le Gall
2007-09-26 22:38 ` [Caml-list] " Vincent Aravantinos
2007-09-26 22:41 ` Vincent Aravantinos
2007-09-26 6:19 ` Cherry-picking modules (was Re: [Caml-list] " skaller
2007-09-26 15:08 ` Michael Furr
2007-09-26 17:12 ` skaller
2007-09-26 17:53 ` Mike Furr
2007-09-26 19:16 ` skaller
2007-10-05 14:42 ` Adrien
2007-10-05 14:58 ` Cherry-picking modules (was Re: [Caml-list] [ANN] OCaml Reins 0.1- " Christoph Bauer
2007-10-05 15:21 ` Adrien
2007-10-05 19:45 ` Cherry-picking modules (was Re: [Caml-list] [ANN] OCaml Reins0.1- " David Allsopp
2007-10-05 3:48 ` Cherry-picking modules (was Re: [Caml-list] [ANN] OCaml Reins 0.1 - " Nathaniel Gray
2007-09-26 7:03 ` Maxence Guesdon
2007-09-26 7:44 ` skaller
2007-09-26 8:53 ` Maxence Guesdon
2007-09-26 10:05 ` Daniel Bünzli
2007-09-26 8:17 ` Daniel Bünzli
2007-09-26 15:32 ` Michael Furr
2007-09-26 15:50 ` Vincent Aravantinos [this message]
2007-09-26 16:42 ` Cherry-picking modules (was " Sylvain Le Gall
2007-09-26 17:38 ` [Caml-list] " skaller
2007-09-26 17:57 ` Vincent Aravantinos
2007-09-26 17:22 ` Cherry-picking modules (was Re: [Caml-list] " skaller
2007-09-26 18:17 ` Daniel Bünzli
2007-09-26 18:45 ` Mike Furr
2007-09-26 19:21 ` skaller
2007-09-26 5:51 ` ExtLib, etc. " David Teller
2007-09-26 20:37 ` [Caml-list] [ANN] OCaml Reins 0.1 - Persistent Data Structure Library Mike Furr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6229FB62-3630-449C-BDDC-AD18FAB05DAE@yahoo.fr \
--to=vincent.aravantinos@yahoo.fr \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).