|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
09 Jul 2004, Stefan Ritt, , Introduction of environment variable MIDASSYS
|
09 Jul 2004, Piotr Zolnierczuk, , Introduction of environment variable MIDASSYS
|
09 Jul 2004, Stefan Ritt, , Introduction of environment variable MIDASSYS
|
09 Jul 2004, Piotr Zolnierczuk, , Introduction of environment variable MIDASSYS
|
09 Jul 2004, John M O'Donnell, , Introduction of environment variable MIDASSYS
|
12 Jul 2004, Stefan Ritt, , Introduction of environment variable MIDASSYS
|
20 Jul 2004, Konstantin Olchanski, , Introduction of environment variable MIDASSYS
|
21 Jul 2004, Stefan Ritt, , Introduction of environment variable MIDASSYS
|
|
Message ID: 19
Entry time: 09 Jul 2004
In reply to: 18
Reply to this: 20
21
|
Author: |
Stefan Ritt |
Topic: |
|
Subject: |
Introduction of environment variable MIDASSYS |
|
|
> Here's my suggestion
> MIDASSYS=/opt/midas-1.9.4 (for example)
I guess we should follow the "standard" as much as possible. MIDASSYS was inspired by
ROOTSYS. Now where do people usually install ROOT? Is it /opt/root-x.x.x or something
else. Some years ago (when I did the last time some linux administration) optional
packages were put into /usr/local by default. I guess you have more experience with
today's tradition, so do whatever you thing is standard.
> so the Linux binaries would go to
> MIDASHOST=i386-pc-linux-gnu
> $MIDASSYS/$MIDASHOST/bin
> $MIDASSYS/$MIDASHOST/lib
Does that mean that the path has to be modified to include $MIDASSYS/$MIDASHOST/bin?
If we put a link to /usr/local/bin, the path does not have to be modified. What about
shared libraries? Does ldconfig know about /usr/local/lib, or $MIDASYS/$MIDASHOST/lib?
> and the shared stuff would go to
> $MIDASSYS/include
> $MIDASSYS/share/drivers
> $MIDASSYS/share/examples
What about /usr/share? Is that a common place for documentatino etc?
Thanks for your advice.
- Stefan |