> A lot of this is ATLAS-added stuff as they seem to do the
> same thing with
> adding a bazillion directories to the PATH-type environemtn variables.
At the cost of repeating myself *that is really bad practice* by ATLAS.
There. I feel better now.
Ignoring SLAC specific issues, this *will* bite others. As I said
before, the length of the PATH (and/or LIBPATH), environmental
variable space is system dependent limited, and one really needs
to keep things short. Using a master bin and/or lib directory
and then linking from there to "other places" (as I think you are
saying BaBar does) for the particular locations of associated
packages is probably the best possible compromise.
I will not even go into the issues of using LIBPATH, which
can (randomly) break other things (thanks to everyone having
their own library overrides to things like malloc - because
they have a better memory allocation scheme).
I know, I am preaching to the choir. It is just that this lesson
should not have to be learned repeatedly. "Those that forget
history are doomed to repeat it". Repeatedly.
Gary
|