Changes between Version 10 and Version 11 of Obsolete/Development/Templates/Components


Ignore:
Timestamp:
Jun 30, 2010, 1:48:59 PM (15 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Obsolete/Development/Templates/Components

    v10 v11  
    1010== Modifying Component Templates ==
    1111
    12 Templates related to components (located in directory `components/xxx` where `xxx` is the component name) '''must never be modified''' in place. These files are imported from Quattor CVS and edits made directly in QWG templates will be lost at next update of the component.
     12Templates related to components (located in directory `components/xxx` where `xxx` is the component name) '''must never be modified''' in place. These files are imported from [https://quattor.svn.sourceforge.net/svnroot/quattor/trunk Quattor repository] on SourceForge and edits made directly in QWG templates will be lost at next update of the component.
    1313
    14 If you need to modify these templates (e.g. to add support for a new configuration option), you need to get a copy of [http://quattor.web.cern.ch/quattor/software.htm Quattor CVS], make your modification and commit your changes in CVS to produce a new version of the component. This requires write access to Quattor CVS : if you don't have such an access, contact the component maintainer (look at `config.mk` file) or ask for write access on Quattor Project mailin list `<project-quattor AT cern.ch>`.
     14If you need to modify these templates (e.g. to add support for a new configuration option), you need to get a copy of the [https://quattor.svn.sourceforge.net/svnroot/quattor/trunk Quattor repository], make your modification and commit your changes to produce a new version of the component. This requires write access to Quattor repository : if you don't have such an access, create a SourceForge account and contact a Quattor developer on the mailing list.
    1515
    1616If you are not familiar with Quattor build tools, here is the steps required to produce a new version of the component :
    … …  
    2121make rpm
    2222}}}
    23  1. Commit your changes : don't do a `CVS commit` directly but use `make` targets. There are 3 targets related to tagging a new release, according to the importance of the change :
     23 1. Commit your changes : you can use plain `svn commit` directly but to produce the new version of the component '''you have to use''' `make` targets. There are 3 targets related to tagging a new release, according to the importance of the change :
    2424   * `release` for minor modifications without new features (increment `r` in `M.m.r-n`)
    2525   * `minorversion` for significant modifications (including new features) but without major redesign of the component (increment `m` in M.m.r-n`)
    … …  
    5353}}}
    5454
    55 '''Reminder''' - If you need to checkout a quattor CVS sourcetree, you can do the following :
    56 {{{
    57 # anonymous login
    58 #export CVSROOT=:pserver:anonymous@isscvs.cern.ch:/local/reps/elfms
    59 
    60 #read write login - change the username !
    61 export CVSROOT=:ext:username@isscvs.cern.ch/local/reps/elfms
    62 export CVS_RSH=ssh
    63 
    64 #cvs co -d <directory> <quattor module>
    65 #for instance :
    66 cvs co -d quattorcvs quattor/ncm-components/lcg-2 quattor/quattor-build-tools
    67 }}}