Hello, On Fri, 2005-12-23 at 01:59, Christian Holm Christensen wrote:
[snip} > > > I also don't know whether upstream would approve of one of my > > improvements. I figured out how to make it unnecessary to set most of > > the Geant 4 environment variables by writing a couple of wrapper > > scripts: "g4make" to run make, and "g4run" to run a Geant 4 executable, > > in a subshell with the relevant env. variables set. (I also wrote a > > couple of scripts, env.sh and env.csh, that people can optionally source > > in their login files instead of using the wrapper scripts if they really > > want a polluted environment namespace.) See the README.Debian in the > > geant4 source package (see below) for more info. > > In my humble opinion, wrapper scripts are ugly. That said, I could > imagine that it would be the best solution (for now) to package GEANT 4 > - it's a mess when it comes to environment variables. However, in the > long run, it'd probably be better to lobby for cleaning the code of > environment variables - after all, GEANT 4 is really a library, not a > specific application. > [snip] What's about the idea to switch to init files? A default in /etc and also a user init file in $HOME. But then it looks more like to be implemented by upstream. Kind Regards, Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
