From: John Max Skaller <skaller@ozemail.com.au>
To: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Dynamically loaded library problems (ocaml-3.05)
Date: Fri, 02 Aug 2002 01:03:20 +1000 [thread overview]
Message-ID: <3D494DB8.4050907@ozemail.com.au> (raw)
In-Reply-To: <20020730161819.GB713@iliana>
Sven LUTHER wrote:
>On Wed, Jul 31, 2002 at 01:08:20AM +1000, John Max Skaller wrote:
>
>>Can I suggest that the directory:
>>
>> /usr/local/lib/ocaml_3.05/
>>
>>might be a better default name? In switching versions around, having to
>>reinstall
>>
>
>Is this not configurable ?
>
Note I said *default* name: i.e. make the default libraries install in
different places.
It's not clear how to manage binaries. What Python does is have
'python1.5' and
'python2.1' both in /usr/local/bin, and then use a symbolic link. Client
can also put symlinks in ~/bin. Not clear to me how to ensure all binaries
are switched around when changing versions. Same applies to man pages.
At present, I just reinstall the version I want to use..which takes
considerable time.
Luckily, I only use optimising compiler, so once a binary is built, it
matter not
which development system is active .. but this won't be so once shared
libraries
are used ..
Anyhow, just a though.. version control is a non-trivial thing.
--
John Max Skaller, mailto:skaller@ozemail.com.au
snail:10/1 Toxteth Rd, Glebe, NSW 2037, Australia.
voice:61-2-9660-0850
-------------------
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-08-01 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 9:45 Hans Ole Rafaelsen
2002-07-30 9:56 ` Xavier Leroy
2002-07-30 15:08 ` John Max Skaller
2002-07-30 16:18 ` Sven LUTHER
2002-08-01 15:03 ` John Max Skaller [this message]
2002-08-01 16:00 ` Sven LUTHER
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=3D494DB8.4050907@ozemail.com.au \
--to=skaller@ozemail.com.au \
--cc=caml-list@inria.fr \
--cc=luther@dpt-info.u-strasbg.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).