From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: roberto@dicosmo.org, caml-list@inria.fr
Subject: Re: [Caml-list] Alternative proposal: COAN
Date: Fri, 28 Feb 2003 11:53:13 +0100 [thread overview]
Message-ID: <20030228105313.GA2850@iliana> (raw)
In-Reply-To: <20030228182016D.garrigue@kurims.kyoto-u.ac.jp>
On Fri, Feb 28, 2003 at 06:20:16PM +0900, Jacques Garrigue wrote:
>
> * Easy installation means that you should be able to download, compile
> and install the desired ocaml program or library in one single
> command, including all the dependencies.
> This does not mean that a binary should be available. A binary will
> only work with a single version of ocaml and all dependencies, which
Yes, but notice that this may also be true for the source version, which
sometimes need to be changed between sucessive ocaml versions. Also,
this does not take into account the fact that the libraries you may use
will change also from time to time.
I have been confronted with this problem quite a bit, and i think we
need to move to something where each library (and ocaml suite) can
advertize its compatibility version. Something akin to the sonames used
by C shared libraries.
I began this move for the ocaml debian package in december, by moving
the libdir to /usr/lib/ocaml/3.06, and have planes to have fully
parallel instalable ocaml packages by the time 3.07 and debian/sarge are
released.
The libdir is only one thing, but there are also the binaries to take
into acount, most important among them is ocamlrun. I would encourage a
move from ocamlrun to ocamlrun-<version> in the standard install, or at
least a configure option to add the version number to all binaries.
The aim of this is to be able to still keep bytecode executables around
which were compiled for older versions, even when you are working with
the new version.
> is way too restrictive. Binaries may be provided on a by OS basis,
> but then it is much more comfortable for users to use the packaging
> system provided by the OS (tgz on FreeBSD, rpms on redhat, deb on
> debian, pkg on OSX, ??? on windows...) If the basic framework is
> right, that work should be easy enough.
You know that there are at least 3 BSD ports of debian, not yet
official though. There is also work on debian/mingw, and debian/djpp
(for plain dos).
> * Dependency resolution and automatic recompilation/reinstallation is
> the core of the problem.
> When you modify an ocaml library, all its dependencies have to be
> recompiled. You certainly want to automate this, and have some
> foolproof system to be able to go back to a stable state. This is
> also an area where a bit of compiler "support" may become necessary.
> At least, have different library directories for different version
> of ocaml, ideally some scheme a la OSX to install several versions
> of the same package in parallel.
Yes, i agree with you on that.
Friendly,
Sven Luther
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-02-28 10:53 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 16:54 Benjamin C. Pierce
2003-02-24 18:24 ` Chris Hecker
2003-02-24 20:17 ` Francois Rouaix
2003-02-24 20:28 ` Basile STARYNKEVITCH
2003-02-24 21:03 ` Brian Hurt
2003-02-24 21:10 ` Brian Hurt
2003-02-24 21:22 ` Benjamin C. Pierce
2003-02-25 10:54 ` roberto
2003-02-25 13:20 ` Sven Luther
2003-02-25 13:36 ` roberto
2003-02-25 16:07 ` Sven Luther
2003-02-25 14:17 ` MikhailFedotov
2003-02-25 17:15 ` Eric C. Cooper
2003-02-25 21:48 ` Michal Moskal
2003-02-25 22:14 ` Lauri Alanko
2003-02-26 14:06 ` Sven Luther
2003-02-27 8:05 ` Blair Zajac
2003-02-27 8:29 ` Xavier Leroy
2003-02-23 16:51 ` Chet Murthy
2003-02-27 15:39 ` [Caml-list] hierarchical modules John Carr
2003-03-01 18:09 ` [Caml-list] " Xavier Leroy
2003-03-01 18:18 ` Michal Moskal
2003-03-02 15:58 ` Xavier Leroy
2003-02-25 22:59 ` [Caml-list] Alternative proposal: COAN Sven Luther
2003-02-26 9:47 ` Michal Moskal
2003-02-26 10:11 ` Sven Luther
2003-02-26 10:26 ` Michal Moskal
2003-02-26 11:53 ` Sven Luther
2003-02-26 10:35 ` Olivier Andrieu
2003-02-26 12:03 ` Sven Luther
2003-02-27 3:19 ` Nicolas Cannasse
2003-02-23 15:05 ` Chet Murthy
2003-02-27 4:54 ` Nicolas Cannasse
2003-02-23 16:13 ` Chet Murthy
2003-02-27 9:20 ` Sven Luther
2003-02-27 10:39 ` Damien Doligez
2003-02-28 9:20 ` Jacques Garrigue
2003-02-28 10:53 ` Sven Luther [this message]
2003-02-28 12:28 ` Jean-Christophe Filliatre
2003-02-28 13:08 ` Markus Mottl
2003-02-28 13:27 ` Sven Luther
2003-02-28 14:05 ` Jean-Christophe Filliatre
2003-02-28 14:43 ` Sven Luther
2003-02-28 15:58 ` Benjamin C. Pierce
2003-03-01 18:03 ` Michal Moskal
2003-03-01 8:14 ` Blair Zajac
2003-03-02 18:21 ` Xavier Leroy
2003-03-02 20:09 ` Sven Luther
2003-03-02 21:38 ` Doug Bagley
2003-03-03 2:39 ` Nicolas Cannasse
2003-03-03 9:07 ` Sven Luther
2003-03-03 9:24 ` Nicolas Cannasse
2003-03-03 9:37 ` Sven Luther
2003-02-26 18:42 Jeff Bowden
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=20030228105313.GA2850@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
--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