caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Thomas Braibant <thomas.braibant@gmail.com>
To: Roberto Di Cosmo <roberto@dicosmo.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Distributed computing libraries
Date: Wed, 6 Jun 2012 16:43:44 -0400	[thread overview]
Message-ID: <CAHR=Vkyra1adaei5LLqL5w8Buxm-J2q4JZ0=h9thBUTQGS_toA@mail.gmail.com> (raw)
In-Reply-To: <20120606202402.GA19265@voyager>

<snip>
> I think OCaml is a wonderful language, and it has the potential
> to attract much more users if we can make it easy to find, build,
> install, compare and assess the various libraries, packages
> and tools that are available.

I completely agree with what you just said, and that was the point of
my question: trying to assess, in a single thread, the  various
possibilities that exist to solve a given problem [1]. Now, it happens
that I had been thinking about the same kind of mail about package
managers, because there is also a huge variety of solutions. So, I
could ask, what are the pros and cons of the following package
managers?

- https://github.com/thelema/odb
- https://github.com/hcarty/ocamlbrew
- https://github.com/OCamlPro/opam
- http://godi.camlcity.org/godi/index.html
- http://oasis.forge.ocamlcore.org/oasis-db.html

But I do not want to fork that thread yet ;).

I think a more general perspective on this was given a while ago on
this list by Xavier, a while ago on this list (trying to paraphrase):
- the community needs a common packaging system
- there is often a lack of convergence between related projects (in
this case, libraries, for instance).

>   And for each "feature" of the language, I'd love to see tutorials,
>   code examples, pointers to the relevant literature, and to
>   packages showing them off.

On a related note, I was delighted to see that there are two books
about OCaml in the pipes currently, and I think this is great.

Thomas
[1] Actually, I did that also a while ago, about openGL bindings, and
the following discussion was quite fruitful

  reply	other threads:[~2012-06-06 20:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06 16:53 Thomas Braibant
2012-06-06 17:31 ` oliver
2012-06-06 17:34   ` Vincent Aravantinos
2012-06-06 18:01 ` AW: " Gerd Stolpmann
2012-06-06 18:16   ` Edgar Friendly
2012-06-06 18:18     ` oliver
2012-06-06 18:35     ` AW: " Gerd Stolpmann
2012-06-06 18:44       ` Edgar Friendly
2012-06-06 20:52   ` Thomas Braibant
2012-06-07  1:34     ` Francois Berenger
2012-06-07 15:44       ` Thomas Braibant
2012-06-08  0:53         ` Francois Berenger
2012-06-08  6:36         ` Francois Berenger
2012-06-06 20:24 ` Roberto Di Cosmo
2012-06-06 20:43   ` Thomas Braibant [this message]
2012-06-07  1:48     ` [Caml-list] OCaml package managers Francois Berenger
2012-06-06 22:23   ` [Caml-list] Distributed computing libraries Ashish Agarwal
2012-06-08  6:55     ` Roberto Di Cosmo
2012-06-11 14:48       ` Ashish Agarwal
2012-06-08  8:58 ` jean-marc alliot

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='CAHR=Vkyra1adaei5LLqL5w8Buxm-J2q4JZ0=h9thBUTQGS_toA@mail.gmail.com' \
    --to=thomas.braibant@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=roberto@dicosmo.org \
    /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).