From: Stefano Zacchiroli <zack@cs.unibo.it>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml packaging problems
Date: Thu, 16 May 2002 20:52:21 +0200 [thread overview]
Message-ID: <20020516185221.GB17601@cs.unibo.it> (raw)
In-Reply-To: <Pine.LNX.4.33.0205161411420.26109-100000@ontil.ihep.su>
On Thu, May 16, 2002 at 02:24:49PM +0400, Vitaly Lugovsky wrote:
> Sure. But distribution packagers, like me, can't wait for
> such a decision. :(
Indeed: with debian we choose a solution to the problem because no one
proposed a standard policy. Now seems that a policy is just to be
issued, well for us, we are only asking to take _one_, _definitely_
decision.
> it will be very nice to have a possibility to split ocaml libraries
> into runtime and development parts. Dynamic libraries belongs to the
Already done in debian packages, for each package that ships a library
that contain shared objects we have two packages: one named libfoo-ocaml
and one named libfoo-ocaml-devel where 'foo' is the name of the library.
The former contains the shared objects, the latter contains all the
other developmente stuff.
> runtime part, and, then, should be handled in an OS native way.
> For Unices it's a libraries located in one big pile like /usr/lib/
Yes, but not /usr/lib itself, something like /usr/lib/ocaml (what a
coincidence! :-) is better, anyway we have a polluted /usr/lib/ocaml
directory so that is better to choose something different like
/usr/lib/ocaml/shlibs or similar. See FHS for more details.
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-16 18:52 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 [this message]
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=20020516185221.GB17601@cs.unibo.it \
--to=zack@cs.unibo.it \
--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