CMT Roadmap

Authors : C.Arnault <arnault@…>, V.Garonne <garonne@…>
Date : 06.21.2005
Version : 0.1

Before end of 2005 we (VG + CA) will carry on the following main tasks:

• SVN migration from CVS
• Source Distribution Kit for the Atlas software

Table of Contents

1. General context
2. SVN migration from CVS
   1. Define a work model for the svn repository
   2. Convert repository from CVS to SVN
      1. Evaluation of the cvs2svn python script
   3. Impact of svn properties (Meta-data) over the code management
   4. Connections with CMT
   5. Consequences and interactions with the tag collector
   6. Consequences for users
   7. Validation phase
   8. Useful links
3. Source Distribution Kit
   1. Goal
   2. Atlas package types
   3. Pacman
   4. Consequences for CMT
   5. Validation phase
4. Miscelleanous

General context

The schedule proposed here naturally fits with the requirements to support the multi-project paradigm that is to be implemented in the next months.

SVN migration from CVS

Define a work model for the svn repository

E.g.:

A/trunk/
A/v1
B/trunk/
B/v1

OR

v1/A
v1/B

trunk/A
trunk/B
trunk/C

Convert repository from CVS to SVN

Christian’s pseudo-codes:

For all packages
  Find all CMT tags (including HEAD)
      For each tag in tags:
          Cvs export –r tag
          svn import CMT/tag

• This approach forgets all intermediate checkins. We only save tags.

Evaluation of the cvs2svn python script

• ​cvs2svn project home
• ​CvsToSvn notes

Impact of svn properties (Meta-data) over the code management

Connections with CMT

• Do we need to rebuild a CMT/SVN pluggin for doing cmt co via SVN ?
  • The repository structure may suppress its need at all

Consequences and interactions with the tag collector

• To be studied together with the TC team

Consequences for users

• Changing the HowTos
• Impact to the work model
• Do a list of concerned commands
  • Options:
    • Wrapped commands
    • New commands

Validation phase

1. Try and validate this for all packages in the atlas project

Useful links

• ​Atlas Wiki
• ​Slides
• ​svn co
• ​CvsToSvn notes
• ​cvs2svn project home

Source Distribution Kit

Goal

1. To have the ability to construct all Atlas software from sources
2. To provide the debug(-dbg) kit with binaries and sources. It could be implemented at the pacman kit creation level.
3. Understand and implement the relationships with source kits of external products

Atlas package types

• There are three different kinds of packages:
  • Atlas internals
  • External products from LCG
  • Atlas externals (eg generators)

For the first category:

1. Test the shell script currently available
2. (Convert it into python)
3. Validate it with the Atlas software

For the second category:

1. SPI is currently working on a way of manipulating and installing external software from sources.
   contact: Yannik patois, Glasgow people (LHCb), ...

For the third category:

1. Prayer is probably the best strategy in waiting…

Pacman

1. Create .pacman file for all tarball.

Consequences for CMT

1. Add the possibility to define a connection to an externally defined pacman kit. Typically through a CMT macro

E.g.:

macro <package>-pacman-link "package ('LCG:Aext')"

Validation phase

1. Try and validate the Atlas software installation on the LAL CE.
2. This exercice could be a good oportunity to validate the Atlas code on MAC (one contiguous issue is also to provide CMT within Xcode environment).

Miscelleanous

• CMT RH7.3/SLC/SLC n+1 compatibility
  1. Should try to use the static compilation option.
     1. Add the static key work in the linking command in the cmt.make file.