caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Dario Teixeira <darioteixeira@yahoo.com>
To: Caml List <caml-list@inria.fr>
Subject: Re: ocamlbuild (was Re: [Caml-list] Re: GODI is shutting down)
Date: Fri, 26 Jul 2013 06:48:17 -0700 (PDT)	[thread overview]
Message-ID: <1374846497.73427.YahooMailNeo@web120401.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CAPFanBG4L_9jZqJPdydNNQysD2ot=mpwZAmSpHsOwv6MeO43Vw@mail.gmail.com>

Hi,

> As I said above, I plan to keep using ocamlbuild and incrementally fix

> some of its shortcomings (parallelization, documentation, plugin
> composability...). I hope that some other users will also make a
> contribution and help to solve some of the issues that have been
> reported on the bugtracker (most of them are not very hard to tackle).
> Wojciech and I eager to welcome patches and review them.

Please consider starting with the documentation, which is IMHO OCamlbuild's
Achilles's heel.  I will go as far as saying that what stopped OCamlbuild from
becoming the ultimate OCaml build tool and thus preempting the constant
popping up of new but often ephemeral build tools was precisely the lack
of good documentation.  Moreover, I reckon that even the other OCamlbuild
shortcomings (namely parallelisation) would have been patched long ago
if the tool had gained the community mind share that it missed due to its
poor documentation.

Daniel has already mentioned some of the things wrong with OCamlbuild's docs.
For me, the most egregious aspect of the manual is the lack of a good narrative
and a bird's eye view of the tool.  One can go through the whole document and
remain wondering how does it actually work and what does it do!  The reader
is thus left without a good mental model of the tool.  Moreover, bear in mind that
the wiki documentation is a good resource only *after* one already understands
how the tool works and what the various entities mean and how they fit together.

Anyway, I'm sure you (Gabriel and Wojciech) are well aware of the points I've just
raised, and time availability is the only limiting factor for improving the situation.
But since you've bravely "inherited" the maintenance of OCamlbuild, my 2 cents
is that your short term move that is likely to wield greater long term benefits is
to write a short introduction that allows the reader to really grok OCamlbuild.

Best regards,
Dario Teixeira

  reply	other threads:[~2013-07-26 13:48 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 21:21 [Caml-list] GODI is shutting down Gerd Stolpmann
2013-07-22 22:32 ` Anil Madhavapeddy
2013-07-23  6:49   ` Gabriel Scherer
2013-07-23  8:46     ` Keyan
2013-07-23  8:57       ` AW: " Gerd Stolpmann
2013-07-23  9:45         ` Paolo Donadeo
2013-07-23 13:31         ` Marek Kubica
2013-07-24  9:09           ` Mihamina Rakotomandimby
2013-07-23  9:34   ` AW: " Gerd Stolpmann
2013-07-23 10:00     ` Jesper Louis Andersen
2013-07-22 23:44 ` oliver
2013-07-23  0:03   ` Nicolas Braud-Santoni
2013-07-23  1:51 ` Francois Berenger
2013-07-24  9:27   ` [Caml-list] " Andreas Hauptmann
2013-07-23  9:07 ` [Caml-list] " Adrien Nader
2013-07-23 10:01   ` AW: " Gerd Stolpmann
2013-07-23 10:22   ` oliver
2013-07-24  1:55   ` Francois Berenger
2013-07-24  7:03     ` Fabrice Le Fessant
2013-07-24  8:42       ` Jun Furuse
2013-07-24 10:30         ` Daniel Bünzli
2013-07-25 14:46           ` [Caml-list] " Sylvain Le Gall
2013-07-24 12:36       ` AW: [Caml-list] " Gerd Stolpmann
2013-07-24 14:44         ` Thomas Gazagnaire
2013-07-24 15:58           ` Markus Mottl
2013-07-24 16:25             ` Thomas Gazagnaire
2013-07-24 16:36               ` Gabriel Scherer
2013-07-24 16:41                 ` Anil Madhavapeddy
2013-07-25 15:21                   ` [Caml-list] " Sylvain Le Gall
2013-07-24 16:39               ` AW: [Caml-list] " Markus Mottl
2013-07-24 16:58                 ` Thomas Gazagnaire
2013-07-24 17:06                   ` Thomas Gazagnaire
2013-07-24 17:33                   ` Török Edwin
2013-07-24 18:49                     ` Markus Mottl
2013-07-25 15:16               ` [Caml-list] Re: AW: " Sylvain Le Gall
2013-07-25 15:29                 ` Leo White
2013-07-25 15:33                   ` Sylvain Le Gall
2013-07-24 16:39             ` [Caml-list] " Anil Madhavapeddy
2013-07-24 17:05               ` Gabriel Scherer
2013-07-24 17:56                 ` Daniel Bünzli
2013-07-24 18:23                   ` Markus Mottl
2013-07-24 20:43                     ` Daniel Bünzli
2013-07-25  5:32                       ` Adrien Nader
2013-07-25  9:52                         ` Daniel Bünzli
2013-07-25 21:01                           ` Adrien Nader
2013-07-25  1:32                 ` Francois Berenger
2013-07-25 15:10                   ` [Caml-list] " Sylvain Le Gall
2013-07-25 15:23                     ` Christopher Zimmermann
2013-07-25 20:03                       ` Adrien Nader
2013-07-26  1:14                         ` ocamlbuild (was Re: [Caml-list] Re: GODI is shutting down) Francois Berenger
2013-07-26  2:43                           ` Peter Groves
2013-07-26  5:02                           ` Gabriel Scherer
2013-07-26  5:26                             ` [Caml-list] Re: ocamlbuild Francois Berenger
2013-07-26  7:25                               ` Wojciech Meyer
2013-07-26  8:07                                 ` Francois Berenger
2013-07-26  9:24                                   ` r.3
2013-07-26 10:48                                 ` Daniel Bünzli
2013-07-26 11:13                                   ` Wojciech Meyer
2013-07-26 17:29                                     ` Ashish Agarwal
2013-07-26  5:29                             ` ocamlbuild (was Re: [Caml-list] Re: GODI is shutting down) Jeff Meister
2013-07-26  6:14                               ` Gabriel Scherer
2013-07-26 13:48                                 ` Dario Teixeira [this message]
2013-07-25 20:18                 ` [Caml-list] GODI is shutting down Wojciech Meyer
2013-07-24 18:04               ` Markus Mottl
2013-07-24 16:18           ` AW: " Matej Kosik
2013-07-24 16:17             ` David Sheets
2013-07-24 16:56               ` Matej Kosik
2013-07-24 17:03                 ` Thomas Gazagnaire
2013-07-25 15:01                   ` [Caml-list] Re: AW: " Sylvain Le Gall
2013-07-24 22:05           ` AW: [Caml-list] " Siraaj Khandkar
2013-07-24 22:06           ` Virgile Prevosto
2013-07-24 22:47             ` Amir Chaudhry
2013-07-24 23:03             ` Anil Madhavapeddy
2013-07-25  5:22               ` Adrien Nader
2013-07-23  9:28 ` [Caml-list] Re: [Godi-list] " Thomas Gazagnaire
2013-07-23 15:32   ` Pierre-Etienne Meunier
2013-07-23 15:37     ` David Sheets
2013-07-23 15:44     ` Daniel Bünzli
2013-07-23 16:19       ` Pierre-Etienne Meunier
2013-07-23 16:26         ` Ashish Agarwal
2013-07-23 16:32         ` Daniel Bünzli
2013-07-23 16:55       ` Virgile Prevosto
2013-07-28 22:29       ` Wojciech Meyer
2013-07-23 19:38     ` Yaron Minsky
2013-07-23 19:49       ` Pierre-Etienne Meunier
2013-07-23 20:02         ` Yaron Minsky
2013-07-23 22:35 ` [Caml-list] " Mike Lin
2013-07-25 16:10 ` [Caml-list] " Sylvain Le Gall
2013-07-25 17:42   ` Daniel Bünzli
2013-07-25 18:52     ` Sylvain Le Gall
2013-07-25 18:28   ` Fabrice Le Fessant
2013-07-25 19:00     ` Sylvain Le Gall
2013-07-25 19:23       ` Yotam Barnoy

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=1374846497.73427.YahooMailNeo@web120401.mail.ne1.yahoo.com \
    --to=darioteixeira@yahoo.com \
    --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).