Closed treydock closed 6 years ago
I have merged the patch then I realized that it just won't work. That is you can install xalt that way but then XALT won't work. Assuming that the prefix is /apps. Then XALT is installed in /apps/xalt/$VERSION and then a symbolic link is made that connects /apps/xalt/xalt and /apps/xalt/$VERSION. The installed version of XALT needs to find the programs it uses at /apps/xalt/xalt/libexec. It only looks there and not in /apps/xalt/$VERSION/libexec.
The reason is that XALT adds code to user programs. Since a user program might only be compiled once for the life of the machine but a site might have multiple versions of XALT. So XALT has to look in a fixed location that is set at configure time.
If you want to test XALT, you'll have to install it twice. Once in a test location an another in a production location.
Ah in that case we'll just have to test using a second install location like you mentioned.
Idea copied from Lmod. Have always found the
make pre-install
pattern useful when installing new versions for testing to avoid updating the symlink.