GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » General » Why is there a hardcoded $PATH in config.sh?
Why is there a hardcoded $PATH in config.sh? [message #15164] Fri, 09 August 2013 13:56 Go to previous message
Andreas Herten is currently offline  Andreas Herten
Messages: 25
Registered: October 2011
Location: Jülich
continuous participant

From: *ikp.kfa-juelich.de
Every time I source the config.sh file from my build directory, my $PATH environment variable is set to the status that it had while compiling.

Is there a particular reason for this?
Why does PandaRoot not extend the $PATH, like every other program does?

For once, I think this is quite illogical. Why should PandaRoot be the program that takes care about what's in this variable?
It's quite a hassle to always remember that everytime you change your $PATH, there's always this one shell script where you have to put the changes in (when you finally have found out that this was the reason it wasn't working before... Rolling Eyes ).
Also it might be a point for PandaRoot beginners and occasional users to stumble over.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: pbarpSystem
Next Topic: Subversion HOWTO
Goto Forum:
  


Current Time: Mon Jan 17 17:43:31 CET 2022

Total time taken to generate the page: 0.02345 seconds