set noclobber interferes with FCC sw setup

[cleonido]

I noticed that unless I comment out the "set noclobber" command in my ~/.bashrc file, the source /cvmfs/fcc.cern.ch/sw/latest/setup.sh command does not succeed, giving me a generic (non) error (*).

The setup.sh script works fine if I remove the "set noclobber" command.

--Christos

(*)

-bash-4.2$ source /cvmfs/fcc.cern.ch/sw/latest/setup.sh
Usage: source setup-all.sh [OPTION]
Prepare the environment to use FCCSW together with the FCC Externals

Options:
   -c, --compiler COMPILER       Source the environment for the specified compiler
   -e, --externals VERSION       Source a given version of the FCC Externals

Examples:
source setup.sh         # Uses the default values, gcc8 compiler and LCG_96b (96b.0.0)
source setup.sh -c gcc9         # Uses the default of LCG Release for gcc9
source setup.sh -c gcc62 -e 94.2.0      # Sets gcc62 and FCC Externals 94.2.0

-bash-4.2$ which fccrun
/usr/bin/which: no fccrun in (/afs/cern.ch/atlas/scripts:/usr/sue/bin:/usr/lib64/qt-3.3/bin:/usr/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/opt/puppetlabs/bin)
-bash-4.2$

[vvolkl]

Hi @cleonido, thanks for this report! I'm not entirely sure which part of the script is not compatible with noclobber, but we are anyway in the process of switching to a spack-based build system, which generates a different type of setup script, based on environment-modules. This new setup file works even with the noclobber option turned on. I'll close this as soon as we are fully switched.