k4geo vs lcgeo

[giovannimarchiori]

Is there a good reason for still using lcgeo environment variables? They are set in parallel with k4geo ones, but not synchronised with them, so if one has a local copy of k4geo installed, lcgeo_DIR might point to k4geo/ in cvmfs/ while K4GEO_dir/ might point to the local copy. Is that OK, or could we either get rid of lcgeo_DIR in favour of K4GEO_DIR? And should K4GEO_DIR point to the local installation rather than the directory in /cvmfs?

example of what happens with latest nightlies:

source /cvmfs/sw-nightlies.hsf.org/key4hep/setup.sh

=>

k4geo_DIR=/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2024-11-04/x86_64-almalinux9-gcc14.2.0-opt/k4geo/1558cdb73e364ff7554cda66888f454ea8f4cb15_develop-ntd66r/share/k4geo
lcgeo_DIR=/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2024-11-04/x86_64-almalinux9-gcc14.2.0-opt/k4geo/1558cdb73e364ff7554cda66888f454ea8f4cb15_develop-ntd66r/share/k4geo

cd k4geo
k4_local_repo

=>

K4GEO=/home/gmarchio/work/fcc/allegro/fullsim/k4geo
k4geo_DIR=/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2024-11-04/x86_64-almalinux9-gcc14.2.0-opt/k4geo/1558cdb73e364ff7554cda66888f454ea8f4cb15_develop-ntd66r/share/k4geo
LCGEO=/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2024-11-04/x86_64-almalinux9-gcc14.2.0-opt/k4geo/1558cdb73e364ff7554cda66888f454ea8f4cb15_develop-ntd66r/share/k4geo
lcgeo_DIR=/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2024-11-04/x86_64-almalinux9-gcc14.2.0-opt/k4geo/1558cdb73e364ff7554cda66888f454ea8f4cb15_develop-ntd66r/share/k4geo