pacman installation of CMT fails if . not in PATH?

[anonymous]

Hi,

I think the pacman kit of CMT can be made more portable if

. setup.sh

commands in it are replaced by

. ./setup.sh

When I run with the stock .pacman file on Ubuntu I'm getting Package tmp/cmt:trusted.caches:http://cern.ch/atlas-computing/links/kitsDirectory/CMT/pacman/cache:CMT not [installed]:

None of the following alternatives succeeded:

.: 1: setup.sh: not found .: 1: setup.sh: not found

this can be avoided by adding . on the PATH or by the change above. I think replacing . setup.sh with . ./setup.sh would be a better practice because the former depends on the way how the shell is invoked and what user already has in the PATH and anyway the intention is to source the setup in the current directory and nowhere else.

Another issue which might be revisited is the invocation of gmake command. I think most of the platforms capable of running Atlas/CMT have GNU make as make but they need not provide an alias gmake. One could modify CMT*.pacman

shellOutputContains ('. ./setup.sh; cmt version', 'v1r20p20070208')

OR shell ('. ./setup.sh; gmake') OR shell ('. ./setup.sh; make')

I think the risk of running of non-gnu make nowadays is much lower than failing because of executing a non-existing gmake instead of make. And of course one can easily test beforehand by make -v.

cheers

Jiri

[/C=FR/O=CNRS/OU=UMR8607/CN=Grigory Rybkin/emailAddress=rybkin@…]

This was resolved.