allow clients to be run unmodified from more locations

[smithdh]

Hello,

Installing the v3 clients package in an alternate location can not work at the moment without modifying the client scripts (i.e. voms-proxy-destroy, voms-proxy-info or voms-proxy-init). The alternate location might be a relocated install and dependencies might also be installed in various locations (e.g. with varying bases).

Please could the client scripts be enhanced so they can run without modifications in situations like those. It is imaged that this would need the user to have a suitable voms client specific environment variable set; e.g. the paths of required jar files. (A list of jar files rather than their containing directories may save the time of scanning the directories, which is what the client script currently does for some jar files).

Thanks, David

[andreaceccanti]

Hi David,

we plan the ship the clients as a single jar in the future and adapt the script accordingly, so that would likely solve the relocation issues.

Thanks Andrea

[smithdh]

Hi Andrea,

Thanks for the information. I suppose packages like jakarta-commons-io, bouncycastle146 and bouncycastle146-mail will still be needed, but won't be shipped in the single jar. In that case we still need to be able to have the voms-proxy-* scripts be able to pass on the locations to java for those too.

Yours, David