From: Stefano Zacchiroli <zack@debian.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml packaging problems
Date: Tue, 14 May 2002 12:45:47 +0200 [thread overview]
Message-ID: <20020514104547.GA22670@cs.unibo.it> (raw)
In-Reply-To: <20020514105452.B11894@pauillac.inria.fr>
On Tue, May 14, 2002 at 10:54:52AM +0200, Xavier Leroy wrote:
> When you install a package that provides a C shared library, you don't
> install it in a package-dependent directory and add a line to
> /etc/ld.so.conf with this directory; you install in /usr/lib or
> /usr/local/lib, perhaps via a symbolic link. I urge everyone to use
> the same scheme for OCaml shared libraries.
Before proposing such a solution is better to reach an agreement among
the community of OCaml libraries developer.
I've built a lot of debian packages containing ocaml library shared and
not. Almost of them assume that all the library files will be installed
to a _single_ directory, including in "library files": ml and mli files,
cm? files and shared objects. Installing all this stuff in a single
directory will cause rapidly name clashes.
The right(TM) solution seems to be: install shared object files in a
single directory listed in OCaml's ld.conf _but_ install all other stuff
in a per-package directory that needs not to be listed in ld.conf.
Right now I know no package that supports two different destination
directory as install flags. This is a tiny problem, but requires changes
in a lot of packages.
Please, don't require that all the library stuff will reside in a single
directory.
Cheers.
--
Stefano Zacchiroli - undergraduate student of CS @ Univ. Bologna, Italy
zack@cs.unibo.it | ICQ# 33538863 | http://www.cs.unibo.it/~zacchiro
"I know you believe you understood what you think I said, but I am not
sure you realize that what you heard is not what I meant!" -- G.Romney
-------------------
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:[~2002-05-14 15:28 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 [this message]
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
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=20020514104547.GA22670@cs.unibo.it \
--to=zack@debian.org \
--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