First, checkout and build timing-board-software, make the ups product, and install it in some temporary staging directory. These steps can be run as yourself or as np04daq:

source /nfs/sw/artdaq/products/setup
setup uhal v2_6_0 -q e15:prof:s64
setup python v2_7_14b
GITLAB_TAG=..... # Whatever the tag of the release is in gitlab
git clone -b $GITLAB_TAG https://:@gitlab.cern.ch:8443/protoDUNE-SP-DAQ/timing-board-software.git ${GITLAB_TAG}-timing-board-software
cd ${GITLAB_TAG}-timing-board-software
make
make UPS_PRODUCT_DIR=/somewhere/on/nfs/sw  ups

The product itself will be installed in /somewhere/on/nfs/sw/protodune_timing/vA_B_C . Eg, for tag v4b2, the product version is v4_1_2. Copy the ups product directory into the main artdaq products area, for which you'll need to be logged in as np04daq:

cd /nfs/sw/artdaq/products/protodune_timing
cp -r /somewhere/on/nfs/sw/protodune_timing/vA_B_C .
cp -r /somewhere/on/nfs/sw/protodune_timing/vA_B_C.version .

You also need to edit the vA_B_C.version file to change the hardcoded paths there, in the (hopefully) obvious way.

To get the board reader to use this new version, two places must be updated: the top-level CMakeLists.txt in dune_artdaq, and the setupDUNEARTDAQ_* scripts. These must both be done in any software installation that needs to use a board reader depending on the new protodune_timing version.

It's possible, but hopefully unlikely, that the qualifiers (ie, the underlying software stack version) of the artdaq build will change. If that happens, the qualifiers of the protodune_timing build have to change to match. They're set in the timing-board-software in config/UPSProductDeclaration.mk and in config/product_deps.template

-- PhilipAndrewRodrigues - 2018-08-31