Add the Geant4 Monte Carlo radiation transport toolkit and its Python bindings.

[christopherpoole]

No description provided.

[7c6f434c]

Is there a reason to package multiple patchlevels of the previous major version (with the same minor version) from the get-go?

[christopherpoole]

When publishing research, authors will make reference to the specific
patched version they used for their simulations. For validation of results
it is important to work with the correct patch version, and subsequently
examine improvements brought about by the latest version. The changes added
to patches are not always trivial when considering the simulation output.
They may make no difference to the software from a development point of
view however.

I will also note that Geant4 has a fixed and regular versioning and release
cycle that is broadly independent of changes made.
On 05/09/2014 3:08 am, "Michael Raskin" notifications@github.com wrote:

Is there a reason to package multiple patchlevels of the previous major
version (with the same minor version) from the get-go?

—
Reply to this email directly or view it on GitHub
#3963 (comment).

[edolstra]

I don't think we should keep multiple versions around to make research results reproducible. If people require that, they should either:

• Record the exact Nixpkgs version used (i.e. the Git commit hash). This way you reproduce everything, including all dependencies.
• Make a private copy of the Geant Nix expression.

[christopherpoole]

Good point. I didn't really consider option one; which is a more powerful
solution.

What I can do is resubmit a pull request including the latest version only,
ignoring older versions. As new versions are released I can update
accordingly. It is then up to the user if they seek older patches or
versions.

This pull request as is, is useful for me, however probably not for the
general case.
On 05/09/2014 7:21 pm, "Eelco Dolstra" notifications@github.com wrote:

I don't think we should keep multiple versions around to make research
results reproducible. If people require that, they should either:

Record the exact Nixpkgs version used (i.e. the Git commit hash). This
way you reproduce everything, including all dependencies.

Make a private copy of the Geant Nix expression.

—
Reply to this email directly or view it on GitHub
#3963 (comment).

[7c6f434c]

This pull request as is, is useful for me, however probably not for the
general case.

You can push a PR where you add all versions you would ever want and
immediately remove all but the latest minors for major branches…

You can locally tag this revision and have quick and easy access to
older versions (checkout the tag and build).

[Fuuzetsu]

@christopherpoole Can you update the PR as per comments, only keeping the latest version?

[knedlsepp]

I was just working my way through all the motif packages. I can't evaluate this expression. This is due to the missing license "g4sl" (https://geant4.web.cern.ch/geant4/license/LICENSE.html) in the licenses.nix file.