From: Alain Frisch <frisch@clipper.ens.fr>
To: Caml list <caml-list@inria.fr>
Subject: [Caml-list] Libraries in the distribution
Date: Thu, 23 Aug 2001 19:37:49 +0200 (MET DST) [thread overview]
Message-ID: <Pine.GSO.4.04.10108231837060.26026-100000@clipper.ens.fr> (raw)
Hello,
there seems to be a consensus that the Str library should be replaced with
Pcre in the standard distribution. I guess that nobody is satisfied with
Str, and that it is kept in the distribution for backward compatibility.
There are currently several levels of "official recognition" for
libraries:
- standard library: more or less what is needed to build OCaml
- OCaml distribution: useful libraries from the Caml team
- CDK: useful 3rd party libraries
- bazar-ocaml: less general or less finished libraries from the Caml team (?)
- other 3rd party libraries
There is also the Debian effort to package OCaml libraries.
In order to add to the confusion:
- the status of the CDK is not really clear; is it an experiment ? will
there be a way for library authors to upgrade their libraries themselves
in the CDK ? will there be official guidelines for a "standard structure
for packages" ?
- some libraries in the standard distribution seems really integrated
with OCaml (bigarray, dynlink, threads), some are almost unavoidable
(Unix), some have 3rd party (or not) counterpart which are generally
considered superior (Str, labltk ?).
- for newcomers, it is not necessarily easy to use libraries that
requires custom runtime environement/toplevel (the good news
is that it seems that there will soon be a support for dynamically
loading library in the runtime environnement).
I don't want to speak for the Caml team, but I'm not sure to see how a 3rd
party library could be included in the standard distribution. The OCaml
distribution follows OCaml releases (of course !), and the author of the
library may want to release more often. Recall that OCaml development does
not follow the bazar model (?); including 3rd party packages is not the
best way to keep control of the development of the language.
I think it is best to keep the OCaml distribution as small as possible,
and to facilitate the installation of other packages. The current CDK
approach seems a bit unrealistic to me: will a few people take in charge
the integration of all 3rd party packages ? Something like CPAN seems
more promising. (I don't see how it could work without the support
or at least an initial impulsion from the Caml team, but they have
probably more interesting things to do. Maybe if would be in the interest
of the Caml Consortium to coordinate 3rd party efforts; is the
status of the Consortium a public information ?)
Beside a small standard distribution and easy to install packages,
there could be more complete distributions (something like the current
CDK), not necessarily maintained by the Caml team.
Just my .02 EUR.
Alain Frisch
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2001-08-23 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 17:37 Alain Frisch [this message]
2001-08-23 18:05 ` Miles Egan
2001-08-23 18:07 ` Markus Mottl
2001-08-24 15:33 ` Fabrice Le Fessant
2001-08-23 18:32 Krishnaswami, Neel
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=Pine.GSO.4.04.10108231837060.26026-100000@clipper.ens.fr \
--to=frisch@clipper.ens.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