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