Geant4 license clarification or standardization

The fact that the Geant4 collaboration chose not to use any of the over 300 standard licenses ( SPDX License List | Software Package Data Exchange (SPDX)) and created yet-another-custom-one is leading to quite some issues and lengthy legal-team discussions, including the removal of Geant4 (geant4 10.7.0 by drbenmorgan · Pull Request #66422 · Homebrew/homebrew-core · GitHub) from Homebrew-core package manager (geant4: delete by Bo98 · Pull Request #72029 · Homebrew/homebrew-core · GitHub, formula by @bmorgan), and its non-compliance with GPL and DFSG (I Challenge Thee), leading to be considered non-free software inside Debian repositories.

Being used by such a huge number of users and physicists, I would like to kindly ask the team / developers to:

Thanks a lot in advance!

PS:
Local homebrew taps as workaround:

1 Like

Ultimately, DFSG compliance is up to Debian Legal to decide - the Geant4 license is what it is in that context. I don’t know what we would or could add to the discussion there.

Re-licensing would be a huge legal undertaking given the history of the project and its copyright holders. Not saying it’s not possible, just that it’s a lot of work.

We’re of course happy if the license gets incorporated in SPDX - but again, I’m not sure what posting on that thread would achieve.

If the goal is a homebrew tap for Geant4, we’d of course welcome contributions and maintainers towards this. GitHub - drbenmorgan/homebrew-geant4: Test tap for Geant4 Homebrew packaging · GitHub was an attempt towards this, but time and other projects intervened.

1 Like

I checked again with Debian, and they confirm that the Geant4 license is not compliant with the DFSG due to "You may not include this software in whole or in part in any patent or patent application in respect of any modification of this software developed by you.". Meaning it cannot be packaged in the Debian main repository.
If at some point Geant4 wants to relicense / eliminate this clause, let us know :wink:

It could be though packaged in the non-free repositories (that are not active by default).