Instructions for Building Patched Version of the ProductionExe

This file is $CDFSOFT2_DIR/FarmTools/doc/patchprocedure.html

Building Patched Version of the ProductionExe(for Production Coordinators)

We would prefer to run a ProductionExe from a real, frozen release such as 4.0.0. However, due to the time that it takes to compile and link such a release using the kai compiler, sometimes we run a patched version instead. This use of a patched release is expected to stop once physics publication quality data is being processed, or when faster compilers become available.

Notes before beginning

Note: 4.0.0 is used as an example of a base release in this document, and 4.0.0i is used as an example of a patched release. Please replace them as needed in the commands below.
Please check that this document is up to date before using it. The pace of change is fairly rapid.
Use your own account for all of the tasks. Do not populate cdfprod0 account with files, since those are often deleted without a warning.

1. Special User Accounts

Offline shifters need access to CDFOPR account. Outgoing shifter has to edit ~cdfopr/.k5login on FCDFLNX3 to add the incoming shifters to it.
to patch ProductionExe offline shifters need write access to Release package in Run II CVS repository. Contact CDF code management team for this.
after the end of the shift access to special accounts will be removed

2. Naming conventions

Patched releases are named by the name of the corrsponding base release plus a letter indicating the patch number (a,b,c etc), for example

        4.3.1b

is patch "b" for release 4.3.1

contents of the patched release 4.3.1b is defined by the file Release/patches/4.3.1b.patches - see example of 4.0.0i.patches

Patching ProductionExe

Consider creating patch "a" to frozen release 4.3.2:

ssh -l cdfopr fcdflnx3
~/ticket

Create the patch test release

setup cdfsoft2 4.3.2
cd /cdf/scratch/cdfopr/testRel
newrel -t 4.3.2 4.3.2a
cd 4.3.2a
relwrite
addpkg Production
addpkg -h FarmTools
addpkg -h Release
gmake FarmTools.bin

use list of patches provided by the offline operations group (comes from the Project Engineer) to create a patch file Release/patches/4.3.2a.patches
- take one of the existing in Release/patches files and copy it into Release/patches/4.3.2a.patches
```
cp Release/patches/4.3.1b.patches Release/patches/4.3.2a.patches
chmod 644 Release/patches/4.3.2a.patches
```
- edit Release/patches/4.3.2a.patches to include the needed list of patches, then run the following commands
```
  checkout_patches 4.3.2a
  gmake nobin
  gmake Production.bin
```
  after which you should have ProductionExe built in bin/$BFARCH
- commit the newly created patch file Release/patches/4.3.2a.patches into repository
```
   cd  Release/patches
   cvs add -m "new" 4.3.2a.patches
   cvs commit -m "patches file for release 4.3.2a" 4.3.2a.patches
   cd ../..
 
```
For more information on the cvs and SoftRelTools see CDF Note 3891

Last updated May 18, 2003 by pasha Murat
Legal Notices