From: gurr@mrs.med.ge.com (David Gurr)
To: itz@transbay.net
Cc: caml-list@inria.fr
Subject: Re: config info
Date: Fri, 19 Mar 1999 16:49:00 -0800 [thread overview]
Message-ID: <199903200049.QAA04125@swag.med.ge.com> (raw)
> > Hi, The installation of ocaml based applications might be
> > simplified if the standard "make install" copied the config lib and
> > the config/Makefile to the library location. Or if this is messy,
> > how about a "make install-devel" that does the copying? Thanks for
> > considering this detail.
>
> Tcl/Tk does this, and I absolutely hate it. First of all, the config
> file is text,
The config lib is not text and could be extended to include all the
config/Makefile info.
> and in GNU-like environments it should go under the
> share tree, not under lib. Second, and more important, it limits
> flexibility in the derived installations.
I *need* inflexiblity. The point of .cmi files is the inflexiblity
of consistency. I need to use the same compiler etc that was used
to build ocaml.
> This is partly a
> "philosophical" issue (see the last sentence of this message), but
> also a practical one: any bug in the original build is automatically
> propagated to the dependent ones.
Since the config lib is used to build ocaml, and the config/Makefile is
used to gen the config lib, if the config file is wrong, your ocaml
build will be wrong and installation of applications is a moot point.
> (With Tcl, this surfaced in the
> naming of shared libraries).
Perhaps I would understand your point if you explained this example.
> Some prefer life simplified; others prefer to keep control of it.
Re: philosophy: Why would knowing what C compiler was used to compile
& link the bytecode interp result in a loss of control?
-D
next reply other threads:[~1999-03-22 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-20 0:49 David Gurr [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-03-16 17:24 David Gurr
1999-03-19 4:04 ` Ian T Zimmerman
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=199903200049.QAA04125@swag.med.ge.com \
--to=gurr@mrs.med.ge.com \
--cc=caml-list@inria.fr \
--cc=itz@transbay.net \
/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