caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Vitaly Lugovsky <vsl@ontil.ihep.su>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: <caml-list@inria.fr>
Subject: [Caml-list] OCaml packaging problems
Date: Tue, 30 Apr 2002 17:28:38 +0400 (MSD)	[thread overview]
Message-ID: <Pine.LNX.4.33.0204301720320.27777-100000@ontil.ihep.su> (raw)
In-Reply-To: <20020430111657.A18782@pauillac.inria.fr>


 Hi!

 I'm having a big troubles packaging OCaml and 3rd party
libraries (like lablGL, lablgtk) in RPM. All the evil is in 
the ld.conf file - foreign libraries should add lines in 
it at the installation.

 The much better approach to the multi-package configurations
is introduced, e.g. in xinetd, new crontabs, and so on - all
external packages writes their configuration files or even
just a symlinks to the special directory. So, it'll be better to
have a special directory like ld.conf.dir/ with symlinks to
the actual dynamic library paths, which will be updated safely
when new packages are installed/removed. But, we've no directory
access functions in the Pervasives library, and Unix library is
not accessible from the runtime - we can't rewrite dll.ml to
use this approach. May be, it'll be nice to provide some basic
directory access functionality from Pervasives?


-------------------
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-04-30 13:24 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   ` Vitaly Lugovsky [this message]
2002-04-30 15:08     ` [Caml-list] OCaml packaging problems 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
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=Pine.LNX.4.33.0204301720320.27777-100000@ontil.ihep.su \
    --to=vsl@ontil.ihep.su \
    --cc=caml-list@inria.fr \
    --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).