From: Reinhard Budde <reinhard.budde@gmd.de>
To: caml-list@inria.fr
Subject: Re: Suggestion for a site-lib directory
Date: Mon, 22 Mar 1999 14:23:23 +0100 [thread overview]
Message-ID: <36F6444B.14B49729@gmd.de> (raw)
Hello,
Gerd Stolpmann wrote:
> Let's consider another example, ocamltk. Usually this package resides in
> /usr/local/lib/ocaml/camltk, and it is not found by default; you have to add a
> -I option to all ocaml* commands. If all packages were installed this
> way, you would have to do setups for every project that uses such packages,
> i.e. modify your makefiles. That's not tolerable if you have many small
> projects.
Besides some large projects , I work on many small projects. I can live
perfectly with -I.
I'm using setup-makefiles that are included in many others. For example
sets the setup-makefile a variable for being used in -I.
Thus changes are reduced to 1 makefile, furthermore any dependant
makefile may change the setup locally (isn't that called implementation
inheritance :-). This way also solves my problem with generating code
for different OS on the same file-system.
Don't add too many bells and whistles, if that isn't really needed.
Often small is beautiful --- and easier to understand.
Reinhard
--------------
Reinhard Budde reinhard.budde@gmd.de
GMD - German National Research Center for Information
Technology
AiS - Autonomous intelligent Systems
D-53754 St.Augustin tel: +2241-14-2417,fax: +2241-14-2324
--
--------------
Reinhard Budde reinhard.budde@gmd.de
GMD - German National Research Center for Information
Technology
AiS - Autonomous intelligent Systems
D-53754 St.Augustin tel: +2241-14-2417,fax: +2241-14-2324
next reply other threads:[~1999-03-22 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-22 13:23 Reinhard Budde [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-03-19 19:34 Gerd Stolpmann
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=36F6444B.14B49729@gmd.de \
--to=reinhard.budde@gmd.de \
--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