Changes between Version 2 and Version 3 of Obsolete/Development/Templates/RepUpdate

Timestamp:

Jul 19, 2006, 1:11:14 PM (18 years ago)

Author:

/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…

Comment:

--

Obsolete/Development/Templates/RepUpdate

@@ -8 +8 @@
 New or modified templates '''should always''' been committed to the QWG [source:templates/trunk repository trunk] first, never directly in a [source:templates/branches branch] or [source:templates/tags tag].
 
-It is quite important not to break the history when a template is moved from one location to another or removed. And the trunk is not a direct copy of a real repository. To help updating the trunk from a real Quattor configuration database, you should use [source:templates/tools/directory_sync directory_sync] tool. '''This tool must be run from a local workspace of QWG [source:templates/trunk repository trunk]'''. This tool updates a trunk directory with the contents of a specified source, doing the following :
+It is quite important not to break the history when a template is moved from one location to another or removed. And the trunk is not a direct copy of a real repository. To help updating the trunk from a real Quattor configuration database, you should use [source:templates/tools/directory-sync directory_sync] tool. '''This tool must be run from a local workspace of QWG [source:templates/trunk repository trunk]'''. This tool updates a trunk directory with the contents of a specified source, doing the following :
  * Removes all `.tpl` files from the destination directory (the directory to update).
  * Copy all .tpl files from the source directory (built by appending destination directory name to source directory root)
@@ -16 +16 @@
 
 You need to fix manually the unexpected differences. Unexpected differences are all the templates that existed in the repository but no longer exist in the local workspace or all the templates copied from the source but not registered in the repository. There are 3 situations :
- * A template has been renamed or moved. In this case, you should revert the change for this template, do the relevant `svn mv` and rerun `directory_sync` to avoid breaking the template modification history.
+ * A template has been renamed or moved. In this case, you should revert the change for this template, do the relevant `svn mv` and rerun [source:templates/tools/directory-sync directory_sync] to avoid breaking the template modification history.
  * Else, if the template existed in the repository but is no longer present in the workspace (flagged `!` by `svn status`), it can be safely removed from the repository with command :
 {{{