GEANT4-4.9.3 Portfile submission

[cristiano.fontana@…]

Here is a proposal for a Portfile of GEANT4. I had many problems putting this up, so any suggestion in well accepted.

Geant4 is a toolkit for the simulation of the passage of particles through matter. Its areas of application include high energy, nuclear and accelerator physics, as well as studies in medical and space science.

[ryandesign (Ryan Carsten Schmidt)]

Congrats on getting this working! Looks like it was pretty involved.

"port lint" shows a number of simple improvements that could be made. I also recommend using fs-traverse instead of foreach ... exec find, as I showed in your previous port clhep in r62792.

Your port needs some shell scripts in the files directory which don't appear to be attached here.

[cristiano.fontana@…]

I forgot to put those in. I fixed the warnings that port lint showed and changed a bit how the shell scripts are patched.

Is there a way to print the build.env? This way I could automatize the creation of env.sh and env.csh

[cristiano.fontana@…]

Added the fs-trasverse constructs as requested.

[ryandesign (Ryan Carsten Schmidt)]

I committed it in r62858 with the additional change that I cleaned up trailing whitespace (reported by "port lint --nitpick").

I would like to make further changes​ however to simplify. I think all the puts commands should go away; users who want that level of detail should run with the -d debug flag, and if you want to add additional information to that output, you use the ui_debug command.

Yes, you can access the contents of build.env like any other tcl variable if you want to build up the env scripts dynamically, which might make things easier for you in the long run.

[cristiano.fontana@…]

I finally got this Portfile working!

Now the provided examples compile and also custom applications.

[ryandesign (Ryan Carsten Schmidt)]

I committed your changes in r63241. We can make separate tickets for any remaining issues.