When sourcing a setup script from a tcsh script, there is no way for tcsh to determine where that setup script actually resides.
This creates problems for localProductsXXX/setup and for the ups setups and setup scripts.
This iteration of localProductsXXX/setup includes a path to itself and is not relocatable.
Under normal development, we expect users to create new localProductsXXX areas, not copy existing localProductsXXX areas. However, it should be possible to copy a localProductsXXX area for use on the grid. For that use case, you do not need the extra mrb definitions, and can just use the ups setup script.
We will fix localProuctsXXX/setup using some of the logic in the ups setups script.
The ups setups script embeds a path to itself. This path is used as a last resort when setups cannot determine where it lives in any other way.
For this reason, if you download and unwind the ups tarball, you should immediately source /full/path/to/setups. This will set the correct path.