Created attachment 267095 [details] sci-physics/geant4-vmc-2.11 ebuild proposition As described in bug: https://bugs.gentoo.org/show_bug.cgi?id=360283 I propose ebuild for Geant4 VMC interface. This ebuild may use optional dependency (via use flag) - VGM (which is attached in another bug report).
i pushed these ebuilds in the science overlay. please test, and when ready i will integrate the changes to the main tree. feel free to modify them (and send pull requests via our github). thanks.
The ebuild from overlay compiles fine for me against geant-4.9.6, but only after I source the script included for backwards compatibility: source /usr/share/Geant4-9.6.0/geant4make/geant4make.sh Otherwise, it fails with peculiar warnings like "You need a ISO C conforming compiler to use the glibc headers". The ebuild attached to this bug here also needed sourcing the appropriate script. I am not sure how to generalize this, but simplest way might be warning the user if the script has not been sourced before (i.e. check environment variables). Such a warning was included in the ebuild attached here, but is not in the version from overlay.
(In reply to Oliver Freyermuth from comment #2) > I am not sure how to generalize this, but simplest way might be warning the > user if the script has not been sourced before (i.e. check environment > variables). Such a warning was included in the ebuild attached here, but is > not in the version from overlay. let me know if geant-vmc-4.2.14a worked without user tweaks(i am not a user of it). may be we should introduce some env variable (github pull requests welcome).
(In reply to Sébastien Fabbro from comment #3) > let me know if geant-vmc-4.2.14a worked without user tweaks(i am not a user > of it). may be we should introduce some env variable (github pull requests > welcome). I just installed it, and no manual sourcing was needed for a successful emerge :-). Sadly I do currently not have the time to dig deeper into the issue and look for a better solution, but I would also hope that this will be solved upstream (i.e. work without the script for backwards-compatibility). If they want to conform with geant4-development, they might as well switch to cmake, which should also solve this problem. If I have more time at hand, I might file an upstream bug about this to get it resolved on their side (unless they already have by then...). Thanks!
About 3 weeks ago geant-vmc-4.2.14b has been released, renaming the ebuild to geant-vmc-4.2.14b.ebuild has immediately emerged a working version for me (not too many changes happened upstream, c.f. http://root.cern.ch/gitweb?p=geant4_vmc.git;a=summary ). Could this be also added to the overlay? Thanks!
About two weeks ago geant-vmc-2.15 has been released, renaming the ebuild to geant-vmc-4.2.15.ebuild produced a working version for me. Note that <geant-vmc-2.15 is incompatible (doesn't even compile) with =geant-4.10.0 (these should probably DEPEND on <sci-physics/geant-4.10.0 ). geant-vmc-2.15 works fine with =geant-4.10.0 , but needs a patch to geant for G4ROOT navigation and optical processes (c.f. https://bugs.gentoo.org/show_bug.cgi?id=496678 ) to fix runtime issues in Geant4 (already applied upstream for next release of Geant according to their bugtracker).
sci-physics/geant-vmc:4 is in the tree now since a while and proxy-maintained by myself, so I guess this can be closed?
Absolutely.
