caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alain Frisch <alain@frisch.fr>
To: Berke Durak <berke.durak@exalead.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] OSR - "Batteries included" - Standardizing syntax extensions and extra libraries
Date: Wed, 05 Mar 2008 12:41:54 +0100	[thread overview]
Message-ID: <47CE8702.6070202@frisch.fr> (raw)
In-Reply-To: <47CE73CB.8070904@exalead.com>

Berke Durak wrote:
> It's not better.  It's not the same thing;  ocamlcs could indeed be 
> implemented
> with ocamlfind.

I think ocamlfind basically solves the technical aspect of this 
OCaml-OSR distribution (although if you are ready to add .cma or -pp 
flags explicitly, just installing all the selected libraries together in 
the same directory as OCaml stdlib would also work).

But of course, the real issues with an extended distribution are not 
technical. Btw, there has already been an attempt to maintain such a 
distribution several years ago (Google for "Caml Development Kit"). It 
might be wise to look at the reasons why it is no longer active.

Some of the issues that need to be addressed:

- what is the intended audience? The will influence both the selection 
process and the motivation of people putting efforts into the distribution.

- what is the process to select new libraries, or to remove existing 
ones? I can imagine that many libraries will have a few supporters and 
no strong opponent, so there is a risk/chance that OCaml-OSR will just 
end up incorporating a huge amount of libraries. It should be decided 
early whether this is a good thing or not.

- what is the policy w.r.t. to upgrades of libraries? It is very common 
that a new version of a library break existing code, so simply upgrading 
as soon as possible might not be the best choice. Should several 
versions of OCaml-OSR be maintained in parallel?

- what should be done when a library doesn't work out-of-the box for a 
new version of OCaml? Should it be removed (temporarily) so as to allow 
an early distribution of OCaml-OSR with the new OCaml?

- who's in charge of maintaining a web site, upgrading libraries, 
testing for several architecture, preparing releases, etc?  This is a 
lot of work, so a collaborative approach might be needed, but 
responsibilities need to be defined.

- will there be binary distributions? (Relying on Debian/Fedora/... 
OCaml developpers does not solve the question for Windows.

- will the addition/upgrade of a single library force to reinstall all 
of OCaml-OSR, or will the distribution be made modular?

- will there be a common place to find the documentation for all the 
selected packages?

- will libraries that depend on C code and/or external components be 
accepted?


-- Alain


  reply	other threads:[~2008-03-05 11:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04 17:12 Berke Durak
2008-03-04 17:50 ` [Caml-list] " Hezekiah M. Carty
2008-03-04 20:27   ` Sylvain Le Gall
2008-03-04 20:55     ` [Caml-list] " David Teller
2008-03-04 21:14       ` Hezekiah M. Carty
2008-03-04 22:35       ` Paolo Donadeo
2008-03-04 22:57         ` Lukasz Stafiniak
2008-03-04 20:31   ` [Caml-list] " Dario Teixeira
2008-03-05  0:30   ` Ed Keith
2008-03-05  2:29     ` Yaron Minsky
2008-03-05  8:57     ` [Caml-list] OSR - "Batteries included" - Standardizing syntaxextensions " David Allsopp
2008-03-05 12:02     ` [Caml-list] OSR - "Batteries included" - Standardizing syntax extensions " Gerd Stolpmann
2008-03-05 15:04       ` Richard Jones
2008-03-05  0:10 ` Richard Jones
2008-03-05 10:19   ` Berke Durak
2008-03-05 11:41     ` Alain Frisch [this message]
2008-03-05 12:36       ` Bünzli Daniel
2008-03-05 14:03       ` Dario Teixeira
2008-03-06 14:21       ` Jim Miller
2008-03-05 15:43 ` Stefano Zacchiroli

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=47CE8702.6070202@frisch.fr \
    --to=alain@frisch.fr \
    --cc=berke.durak@exalead.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).