pschecklibs, pscheckperl, psbuild use 'csh psconfig.csh' instead of 'csh -f psconfig.csh'

[Michael Wood-Vasey]

pschecklibs and pscheckperl both use calls out to 'csh psconfig.csh' to determine libdir, bindir, etc. This means it uses your .cshrc configuration files and overrides current settings. It's also somewhat slower to completely sources the .cshrc* files everytime.

Would it be OK to replace these with 'csh -f psconfig.csh' so that it used your current environment configuration? This is particularly relevant for making these work right from bash. Or is the loading behavior of 'csh psconfig.csh' desired?

I got caught up by this when my cshrc and bashrc files referred to different versions of the IPP pipeline. I didn't think that would have been a problem and in a theoretically ideal world I don't think it should be. But this isn't high priority.