ups override file
The setup script will recognize a file in the product database directory named ups_OVERRIDE.`hostname` This is quite handy.
It seems a better idea to look for this file in the .upsfiles directory, so that bunches of them are not floating around in some top level products directory.
We need the ability to override a single flavor regardless of hostname. So we propose adding a file named ups_OVERRIDE.<flavor>.
Finally, the setups script needs to also recognize these files.
#1 Updated by Marc Mengel over 3 years ago
#2 Updated by Marc Mengel over 3 years ago
Okay, so the revision stuff for cvs is wonky; added:
# # set UPS_OVERRIDE based on $PRODUCTS/.upsfiles # s_setenv UPS_OVERRIDE_FILE /dev/null test -r $UPS_THIS_DB/.upsfiles/ups_OVERRIDE.`hostname` && \ s_setenv UPS_OVERRIDE_FILE $UPS_THIS_DB/.upsfiles/ups_OVERRIDE.`hostname` test -r $UPS_THIS_DB/.upsfiles/ups_OVERRIDE.`uname -r | cut -d. -f 1-2` && \ s_setenv UPS_OVERRIDE_FILE $UPS_THIS_DB/.upsfiles/ups_OVERRIDE.`uname -r | cut -d. -f 1-2` s_setenv UPS_OVERRIDE "`cat $UPS_OVERRIDE_FILE`" s_unsetenv UPS_OVERRIDE_FILE