Opened 2 years ago

Last modified 2 years ago

#58319 assigned defect

geant4.10.5 @4.10.05_0+gdml+qt5+threads: very disordered directories

Reported by: frankliuao (Ao Liu (frankliuao)) Owned by: mojca (Mojca Miklavec)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: mojca (Mojca Miklavec)
Port: geant4.10.5

Description

After installation, sourcing the /opt/local/libexec/Geant4/Geant4.10.5/geant4.sh

won't recognize the folder where Data was installed. This was because the data dir was set to ${prefix}/share/Geant4/Data/Geant4.${geant.version}

while the script (auto generated by Geant4) is looking for data in $geant4_envbindir/../../../share/Geant4/Data/Geant4.10.5/

This is a very simple fix: just eliminate using the libexec at all, since it's only used for a few setup scripts. They all can be put in the same folder as in /opt/local/share/Geant4/Geant4.10.5/*sh

First time making a suggestion on a portfile. Not sure how it works. I can make a branch from my side and create a pull request if that's OK, but probably the PR is only accepted if it's submitted by the owner of the port?

Change History (2)

comment:1 Changed 2 years ago by mojca (Mojca Miklavec)

Owner: set to mojca
Status: newassigned
Version: 2.5.4

Contributions from anyone are warmly welcome, so please do submit a pull request (it's not 100% clear what you suggested, a PR will clarify that).

I haven't been using Geant since probably 10.1 or so, and also wouldn't mind an active user helping with maintenance.

comment:2 in reply to:  1 Changed 2 years ago by frankliuao (Ao Liu (frankliuao))

OK. Need a few details for the portfile development. Could you email me ao [at] aoliu.tech

Some help on testing a portfile is appreciated. Thanks!

Ao

Replying to mojca:

Contributions from anyone are warmly welcome, so please do submit a pull request (it's not 100% clear what you suggested, a PR will clarify that).

I haven't been using Geant since probably 10.1 or so, and also wouldn't mind an active user helping with maintenance.

Note: See TracTickets for help on using tickets.