Changes between Version 12 and Version 13 of VincentFAQ

Timestamp:

May 6, 2005, 6:03:52 PM (21 years ago)

Author:

garonne

Comment:

--

VincentFAQ

@@ -1 @@
-= General CMT FAQ =
-
-by V.Garonne                                                   [[BR]]
-Date: 05.4.2005                                                [[BR]]
-Version : 0.1                                                  [[BR]]
-Web site: [http://www.cmtsite.org/ http://www.cmtsite.org/]    [[BR]]
-
-= General Information =
-
-== What is CMT ? ==
-
-[http://www.cmtsite.org/ CMT](__C__onfiguration __M__anagement __T__ool) is a configuration management environment, based on some management conventions and comprises several shell-based utilities. It is an attempt to formalize software production and especially configuration management around a package-oriented principle.
-
-The environment provides conventions (for naming packages, files, directories and for addressing them) and tools for automating as much as possible the implementation of these conventions. It permits to describe the configuration requirements and automatically deduce from the description the effective set of configuration parameters needed to operate the packages (typically for building them or using them).
-
-== What is a package ? ==
-
-The notion of packages represents hereafter a set of software components (that may be applications, libraries, tools etc...) that are to be used for producing a system or a framework. In such an environment, several persons are assumed to participate in the development and the components themselves are either independent or related to each other.
-
-== How to install CMT ? ==
-
-See: [http://www.cmtsite.org/install.html Install]
-
-== Are there copyright restrictions on the use of CMT ? ==
-
-Not really. CMT is provided as an Open-Source product, with available sources, and is opened to any contribution from anybody.
-
-See the license page [http://www.cecill.info/licences.en.html agreement] to find further explanations and a link to the full text of the license.
-
-== How do I get documentation on CMT ? ==
-
-All documentation is available on-line, starting at [http://www.cmtsite.org/documents.html Documents].
-
-== Is there a mailing list devoted to CMT ? ==
-
-There is a mailing list, [http://www.cmtsite.org/discussion.html mailing list].
-
-== I've never used CMT before. Is there a CMT tutorial? ==
-
-There are numerous tutorials avalaible here:
-
- *  [http://www.cmtsite.org/documents.html Documents]
-
- * [http://atlas.web.cern.ch/Atlas/GROUPS/SOFTWARE/OO/sit/Policy/ Atlas and CMT]
-
- * [wiki:VincentTrial How do i begin playing with CMT ?]
-
-== How do I submit bug reports for CMT ? ==
-
-To report a bug, please use the relevant service from the Trac project.
-
- * Bugs: [http://trac.lal.in2p3.fr/CMT/newticket New Ticket] 
-
-
-= CMT in the real world =
- 
-==  How stable is CMT ? ==
-
-Very stable (of course :) ).
-
-== How many people are using Python ? ==
-
-CMT is an academic project aimed at providing support to the software developments in the context of large physics experiments ([http://atlas.web.cern.ch atlas],[[BR]][http://lhcb.web.cern.ch/lhcb/ lhcb], ...).
-
-Although it is currently used by Physics experiments, it is strongly required to stay experiment neutral, and this requirements is fully endorsed in its internal design (eg by ensuring that all possible customizations can always be performed without modifications to the kernel).
-
-This kind of requirements also implies that portability or modularity issues (including environment independance) are assigned a quite high priority. 
-
-== What are the supported platforms ? == 
-
-CMT has been ported and tested on a wide range of machines/operating systems, including:
-
- * DEC-Unix V4.0
- * HP-UX-10 (several types of platforms)
- * AIX-4
- * Solaris
- * IRIX
- * Several variants of LynxOS
- * All variants of Linux (RedHat, Debian, SuSe, ScientificLinux, ...)
- * Windows 95/98/NT/Windows2000 in various environments:
-    * CYGWIN_NT-5.1 environment
-    * nmake based environment
-    * MSDev/VisualC 6 environment
-    * MSDev/VisualC 7 environment
- * Darwin (Mac OS X)
-
-== CMT's design == 
-
-= What are the architecture of the environment ? = 
-This environment is based on the fact that one of its packages (named CMT ) provides the basic
-management tools. CMT , as a package, has very little specificities and as such itself obeys the
-general conventions.
-Then the complete software base is organized in terms of projects (or sub-projects ), containing
-consistently managed package sets. Projects are localized either globally or individually:
-globally using the environment variable CMTPROJECTPATH that describes all locations
-where CMT projects can be found individually using the environment variable CMTPATH that describe all package areas where packages can be found Packages are localized respectively to the projects they belong to.
-It should be noted that the choice of a location for installing CMT itself is totally independent of
-the locations where projects are installed and managed.
-
-CMT is operated through one main user interface : the cmt command, which operates the CMT
-conventions and which provides a set of services for :
- * creating a new package. This operation will create or check the local package directory tree and generate several minimal scripts (see the description of the create command),
- * describing or monitoring :
-    * the relationships between the package and other packages
-    * the configuration features either specified in the current package, or imported from related (used ) ones. (symbols, patterns, fragments)
-    * the constituents of the package in terms of libraries, executables, or generated documents.
- * automatically generating the reconstruction scripts (makefiles ) from this description.
- * recursively acting upon the hierarchy of used packages.
-
-Several other utilities are also provided for some specific activities (such as the automatic
-production of shared libraries, C prototypes, management of interactions between CVS and CMT
-itself, the management of a similar architecture for Windows or OS9 , setting up protections for
-packages (through locks) etc...).
-
-= User FAQ = 
-
-== How to create a package ? ==
-
- cmt create <package_name> <version>
-
-== Does the "requirements" file support comments ? ==
-
-Yes. A comment starts with a hash character (#) that is not part of a string literal, and ends at the end of the physical line.
+{{{
+#!rst
+
+.. contents::
+.. sectnum::
+
+-----
+
+.. ** DOC SVN **
+
+Doc SVN
+=======
+
+Récupération du bouquin de référence
+------------------------------------
+
+(`le site`_ et `la doc locale`_  (Version 1.1 - Revision 12923))
+
+.. _`le site`: http://svnbook.red-bean.com/
+.. _`la doc locale`:
+file:///Users/Shared/Docs/Programmation/Outils/Subversion/svnbook.red-bean.c
+om/en/1.1/index.html
+
+::
+
+   $> cd /Users/Shared/Docs/Programmation/Outils/Subversion
+   $> swget http://svnbook.red-bean.com/en/1.1/index.html
+
+
+.. ** MANIPULATION DE REPOSITORY **
+
+Manipulation de repository
+==========================
+
+Création d'un repository de test
+----------------------------------
+
+(je ne sais pas forcer le groupe via ''sudo'', donc 2 commandes)
+
+::
+
+  $> svnadmin create --fs-type fsfs SVNNEW
+
+ou
+
+::
+
+  $> svnadmin create --fs-type bdb SVNNEW
+
+::
+
+  $> sudo chown -R www:svn SVNNEW
+  $> sudo chmod -R g+w SVNNEW
+
+Passage d'un repository à l'autre
+---------------------------------
+
+::
+
+  $> sudo svnadmin dump /Users/Shared/Roscoff > SVN-Roscoff.dump
+  $> sudo svnadmin load /Users/Shared/SVNTEST < SVN-Roscoff.dump
+
+Par contre, 
+
+::
+
+  $> sudo -u www svnadmin load --parent-dir Roscoff ./SVNNEW <
+SVN-Roscoff.dump
+
+ne marche pas si le répertoire Roscoff n'existe pas dans le repository; je
+crée ce dernier via le serveur HTTP pour des raisons de droits d'accès
+('''rw''' pour ''www'', '''r''' seulement pour le groupe ''svn''):
+
+::
+
+  $> svn mkdir -m "Creation directory Roscoff"
+http://127.0.0.1:8800/Svn/test/Roscoff
+  $> sudo -u www svnadmin load --parent-dir Roscoff ./SVNTEST <
+SVN-Roscoff.dump
+
+
+Exemple de réorganisation d'un repository
+-----------------------------------------
+::
+
+  $> svn list http://localhost:8800/Svn/SVN
+  $> svn mkdir -m "Creation du repertoire Roscoff"
+http://localhost:8800/Svn/SVN/Roscoff
+  $> svn move -m "Deplacement du repertoire FW dans Roscoff"
+http://localhost:8800/Svn/SVN/FW http://localhost:8800/Svn/SVN/Roscoff/FW
+
+
+Migration de DB Berkeley à FSFS
+-----------------------------------------
+::
+
+  $> sudo /sw/sbin/apachectl stop
+  $> sudo svnadmin dump SVN > ~/SVN.dump
+  $> sudo mv SVN SVN-BREAK
+  $> sudo svnadmin create --fs-type fsfs SVN
+  $> sudo chown -R www:svn SVN
+  $> sudo chmod -R g+w SVN
+  $> sudo svnadmin load SVN < ~/SVN.dump
+  $> sudo /sw/sbin/apachectl start
+
+
+Suppression d'un répertoire importé par erreur
+----------------------------------------------
+::
+
+  $> sudo /sw/sbin/apachectl stop
+  $> sudo svnadmin dump /Users/Shared/Svn/COOL > ~/Temp/COOL-dump
+  $> cat ~/Temp/COOL-dump | svndumpfilter exclude Sites/Perf/Database >
+~/Temp/COOL-new-dump
+  $> sudo mv COOL COOL-bak
+  $> sudo svnadmin create --fs-type fsfs COOL
+  $> sudo chown -R www:svn COOL
+  $> sudo chmod -R g+w COOL
+  $> sudo svnadmin load COOL < ~/Temp/COOL-new-dump
+  $> sudo /sw/sbin/apachectl start
+
+Il semble qu'on ne puisse supprimer que des répertoires et non des fichiers
+individuellement.
+
+.. ** GESTION D'UN PACKAGE **
+
+Gestion d'un package
+====================
+
+Import
+--------
+::
+
+  $> cd ~/Projets/Atlas
+  $> svn import -m "Import de IOVDbSvc" IOVDbSvc
+http://localhost:8800/Svn/SVN/Atlas/IOVDbSvc
+  $> svn list http://localhost:8800/Svn/SVN/Atlas
+
+On importe la *copie* de travail locale **vers** le *dépot*.
+
+Examen
+----------
+::
+
+  $> svn list --verbose http://localhost:8800/Svn/COOL/
+
+L'option ''--verbose'' rajoute le numéro de révision, l'auteur et la date de
+révision pour chaque répertoire.
+
+*Check out*
+--------------
+::
+
+  $> svn co http://127.0.0.1:8800/Svn/SVN/Atlas/IOVDbSvc IOVDbSvc
+
+On récupère le répertoire du *dépot* **vers** la *copie* de travail locale.
+
+Update
+--------
+::
+
+  $> 
+
+Tagging
+---------
+::
+
+  $> svn copy http://localhost:8800/Svn/SVN/Atlas/IOVDbSvc \
+              http://localhost:8800/Svn/SVN/Atlas/IOVDbSvc-00-01-47 \
+              -m "Tagging IOVDbSvc-00-01-47"
+
+*Correction* d'un tag
+-------------------------
+Deux stratégies possibles :
+
+- corriger dans la *branche principale*, supprimer le tag obsolète et
+re-tagger (méthode utilisée par Michel)
+
+::
+
+  $> svn rm http://localhost:8800/Svn/COOL/Sites/Perf-00-00-03 \
+              -m "Suppression tag Perf-00-00-03 pour application patch - Cf
+source:Sites/Perf_ChangeLog"
+  $> ci -m "Corrections et patch -  Cf source:Sites/Perf_ChangeLog"
+  $> svn copy http://localhost:8800/Svn/COOL/Sites/Perf \
+              http://localhost:8800/Svn/COOL/Sites/Perf-00-00-03 \
+              -m "Nouveau tag Perf-00-00-03"
+
+- introduire le patch (corriger) dans la *branche taggée* puis mettre à jour
+la branche principale (merge) (méthode *Christian*)
+
+.. ** GESTION DES 'PROPERTIES' **
+
+Gestion des 'properties'
+========================
+
+svn:ignore
+----------
+
+On donne à **Subversion** la liste des fichiers à ignorer en définissant la
+*property* **svn::ignore** sur les répertoires.
+
+À partir d'une liste de fichiers (par exemple *.cvsignore*) :
+
+::
+
+  $> svn propset -R svn:ignore . -F .cvsignore
+
+ou bien en éditant directement la *property* :
+
+::
+
+  $> setenv SVN_EDITOR vi
+  $> svn propedit svn:ignore .
+
+Les *properties* sont versionnées :
+
+::
+
+  $> svn commit -m "Ignoring ignorable files"
+
+
+.. ** ADMINISTRATION DU DÉPOT **
+
+Administration du dépot
+========================
+
+recover
+----------
+
+Il faut absolument penser à **arêter le serveur apache** avant de toucher au
+dépot.
+
+::
+
+  $> sudo /sw/sbin/apachectl stop
+  $> sudo svnadmin recover SVN
+  $> sudo svnadmin verify SVN
+  $> sudo /sw/sbin/apachectl start
+
+dump/load
+------------
+
+Quand on ne se sort pas d'une erreur *FATAL*, on peut tenter ça :
+
+::
+
+  $> sudo svnadmin SVN > ~/SVN.dump
+  $> sudo mv SVN SVN-BAK
+  $> sudo svnadmin create SVN
+  $> sudo chown -R www:svn SVN
+  $> sudo chmod -R g+w SVN
+  $> sudo svnadmin SVN < ~/SVN.dump
+
+Ce type de manip a disparu en passant en *fsfs* Š
+
+}}}