caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven Luther <luther@lambda.u-strasbg.fr>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: Sven <luther@dpt-info.u-strasbg.fr>,
	Vitaly Lugovsky <vsl@ontil.ihep.su>,
	caml-list@inria.fr
Subject: Re: [Caml-list] OCaml packaging problems
Date: Thu, 13 Jun 2002 17:50:01 +0200	[thread overview]
Message-ID: <20020613155001.GA27493@lambda.u-strasbg.fr> (raw)
In-Reply-To: <20020514105452.B11894@pauillac.inria.fr>

On Tue, May 14, 2002 at 10:54:52AM +0200, Xavier Leroy wrote:
> So, to summarize, I strongly suggest the following approach for RPMs
> or Debian packages:
> - The main Caml package can add one or two lines to ld.conf,
>   e.g. /var/lib/ocaml/shlibs (for libraries installed by other packages)
>   and /usr/local/lib/ocaml/shlibs (for local stuff)
> - Packages for additional Caml libraries install their shared libraries
>   in /var/lib/ocaml/shlibs, either directly or via a symlink.

Xavier, ...

I am going to prepare a new ocaml debian package which will support what
you suggest, but still be compatible with the current way of doing
things (using the external ocaml-ldconf program).

What i will do is have the ocaml-base package (which contains the
minimum needed to run bytecode programs only, namely ocamlrun and the
dll.so) add /usr/lib/ocaml/shlibs for stub libraries provided by a
debian package, and /usr/local/lib/ocaml/shlibs for stub libraries
provided by third party libraries.

Debian packaged library will move the dll.so into these directories, and
everything will be fine, but older packages or packages with lazy
maintainers will still be able to use ocaml-ldconf.

Third parties libraries (that is, non debian packaged ones) which use findlib
will know about this scheme, and use the debian package version of findlib to
install stuff in the proper place (/usr/local/lib/ocaml/shlibs).

Third party libraries which do not use findlib, either don't know about
dll.so, and in this case there is no problem, or try to install them
either in /usr/lib/ocaml (which is bad) or add a file by hand into
/usr/lib/ocaml/ld.conf.

In this later case, i will try to prevent this from happening, and make
people aware that this is not the correct way of doing this (if we agree
on that, that is).

But there are two points i much would like a consensus being attained on
:

1)  What will be the exact name of these directories ? It would be a good
idea, i think at least, if we choose the same name for all
installations of ocaml, and not everyone choosing it's own directory.
(or else we could have a ocaml option similar to -where which would
give a pointer to these directories ? and have the choice of the
directory highly configurable, maybe a -where_stub or something such ?)

Actually i have the proposition of "shlibs" from you, and "libexec" from
Gerd and the findlib people. and then i feel myself "stublibs" should be
a nice name too, especially since it is just the sub libraries we are
speaking about, and not the .cma and other such ocaml libraries.

2) I think it would be nice to distinguish two such directories,
/usr/lib/ocaml/shlibs for distribution native libraries (the packaged
ones that follow the rule), and /usr/local/lib/ocaml/shlibs for hand
installed packages. What precedence should we take for them by default ?

And should these two dirs be hardcoded into the ocaml suite, (as are
/usr/lib and /lib into the C ld.so) ?

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


  parent reply	other threads:[~2002-06-13 20:57 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
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 [this message]
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=20020613155001.GA27493@lambda.u-strasbg.fr \
    --to=luther@lambda.u-strasbg.fr \
    --cc=caml-list@inria.fr \
    --cc=luther@dpt-info.u-strasbg.fr \
    --cc=vsl@ontil.ihep.su \
    --cc=xavier.leroy@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).