To the LibrarianIssues page To the SPI WorkBook page

How to update the configurations for LCG AA

Updating the SCRAMToolBox

Check out the scram toolbox :

cvs -d :kserver:spitools.cvs.cern.ch:/cvs/SPITOOLS co SCRAMToolBox
cd SCRAMToolBox

Make sure the head is the version you want to start with by checking against the existing tags of all the actual configurations:

cvs -n update -r LCG_34
cvs -n update -r LCG_34_1
cvs -n update -r LCG_34_2

If one of these shows a difference, check the file which differs and make sure with the corresponding project that the change is ok.

Updating a version of an (existing) external package

Now edit the following files and make sure you update the version in all places in the file:

  • Configuration/Configuration
  • LCGconfigs/tools-CERN.conf make sure you replace the version in all places
  • The tool file for the package: search for it in the other directories.

In the tool file for the package, change the version in the line: <Tool name=XXX version=YYYa> . If the tool file contains several "blocks" of identical code, duplicate the one with the highest version and change the version in the duplicate.

Once you have changed all these places, check back in and tag "LCG_NN"

Updating a version of the LCG AA project(s)

Ideally, the project versions should only appear in their corresponding "level tag", such that LCG_NN only contains the externals, LCG_NN_1 contains the externals and project without any other dependencies like SEAL and GENSER and LCG_NN_2 contains the set of LCG_NN_1 plus the projects depending on these, like POOL and PI (for use e.g. in COOL which needs POOL).

In practice this is not true and all the projects are put in at all levels, so the "higher level tags" are practically the same as the "base tag". Differences may occur if a "higher level" project discovers the need for changing an external package (version) while preparing for the release. Of course any change for an external used in a "lower level" project needs to be discussed and validated by the concerned project.

To update the configuration for the projects, edit the following files and make sure you update the version in all places in the file:

  • Configuration/Configuration
  • LCGconfigs/tools-CERN.conf make sure you replace the version in all places
  • The corresponding project file(s) in LCG/Tools

Updating for a new platform

For adding (or removing) a platform, first check out (or update) the toolbox. Then make sure you add (or remove) the corresponding entry in the configuration file (Configuration/Configuration) and the tools file (LCGconfigs/tools-CERN.conf). For the latter, it's easiest to copy/paste an existing block and then update all the references to the platform.

If the new platform has the need for a new compiler tool, then add the corresponding file to the Compilers/XXX/ directory, otherwise make sure the selected tool file is ok with your architecture (e.g., for amd64/gcc344 we could reuse the existing compilers, just adding the new version to the CXX (gcc3) and Fortran (g77gcc3 compiler tool files).

Then do a grep -l -R Architecture * to find all the files which have specific entries for architectures (typically different names for libraries) and make sure your changes are consistent in these files as well.

Then try to build a project to make sure things are ok ...

-- AndreasPfeiffer - 21 Jun 2005

Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r5 - 2006-08-23 - AndreasPfeiffer
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    SPI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback