caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml packaging problems
Date: Wed, 15 May 2002 10:18:17 +0900	[thread overview]
Message-ID: <20020515101817V.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <20020515005240.A629@ice.gerd-stolpmann.de>

While I was trying to answer on the limitations of the Unix approach,
Gerd Stolpmann posted a much better and well-argument description of
the problem.

To complement this, I would add a suggestion to make the current
scheme work more smoothly.  It takes its inspiration from java's
classpath, which seems to work pretty well:
Couldn't we replace the single directory in OCAMLLIB by a path.
Alternatively, there could be an OCAMLPATH, taking precedence on
OCAMLLIB.
This path would replace the current stdlib for everything:
* it would be a default path for searching caml libraries and dlls
* ld.conf's under each of its elements would be read in its order
* +dirname on the command line would expand to elt/dirname for each
  of its elements
* findlib might honour it too

This would in particular solve the current problem with users who do
not have write access on the main library tree, and allow more
flexibility. This is of course orthogonal to the dependency handling
done by findlib.

For library designers, they would just have to honour this
variable by installing by default under the first element of this
path, adding the directory to elt/ld.conf if they also install dlls.

In my opinion simple (one variable), standard (think Java), and clean.

Jacques
-------------------
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


  reply	other threads:[~2002-05-15  1:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22 13:07 [Caml-list] Project Proposals Diego Olivier Fernandez Pons
2002-04-30  9:16 ` Xavier Leroy
2002-04-30 13:28   ` [Caml-list] OCaml packaging problems Vitaly Lugovsky
2002-04-30 15:08     ` Remi VANICAT
2002-04-30 18:04     ` Sven
2002-05-14  8:54       ` Xavier Leroy
2002-05-14 10:45         ` Stefano Zacchiroli
2002-05-14 15:46           ` Xavier Leroy
2002-05-14 11:39         ` Jacques Garrigue
2002-05-14 13:54           ` Michal Moskal
2002-05-14 23:28             ` Jacques Garrigue
2002-05-15 12:10           ` Sven Luther
2002-05-14 13:49         ` Michal Moskal
2002-05-14 22:52         ` Gerd Stolpmann
2002-05-15  1:18           ` Jacques Garrigue [this message]
2002-05-15 12:05         ` Sven Luther
2002-05-15 17:39           ` Vitaly Lugovsky
2002-05-16  7:11             ` Sven Luther
2002-05-16 10:24               ` Vitaly Lugovsky
2002-05-16 18:52                 ` Stefano Zacchiroli
2002-05-17 16:05                 ` Sven Luther
2002-05-17 19:31                   ` Vitaly Lugovsky
2002-05-18 10:39                     ` Michal Moskal
2002-05-21 19:54                     ` Sven Luther
2002-06-13 15:50         ` Sven Luther
2002-06-18 12:57           ` Xavier Leroy
2002-06-18 13:32             ` Sven Luther
2002-06-18 20:04               ` Gerd Stolpmann
2002-06-19  6:33                 ` Sven Luther
2002-06-19 11:09                   ` Markus Mottl

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=20020515101817V.garrigue@kurims.kyoto-u.ac.jp \
    --to=garrigue@kurims.kyoto-u.ac.jp \
    --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).