Parallel directory structures take their structure from one unique
-parent directory structure. Inside CentOS Artwork Repository, this
-unique parent directory structure is under `trunk/Identity'
-directory. The `trunk/Identity' directory structure must be
-considered the reference for whatever information you plan to create
-inside the repository.
+
Parallel directories take their structure from one unique parent
+directory. Inside CentOS Artwork Repository, this unique parent
+directory is under `trunk/Identity' location. The
+`trunk/Identity' location must be considered the reference for
+whatever information you plan to create inside the repository.
In some circumstances, parallel directories may be created removing
uncommon information from their paths. Uncommon path information
@@ -274,12 +273,12 @@ build the parallel directory used to retrived translations, and
pre-rendering configuration scripts required by render
functionality.
-Another example where parallel directory information is built by
-removing the uncommon path information is when we use the help
-functionality. This time, `centos-art.sh' script uses parallel
-directory information (without uncommon directory levels) to build the
-documentation entry required by Texinfo to store directory
-documentation inside the repository.
+
Another example where parallel directory removes the uncommon path
+information is when we use the help functionality. This time,
+`centos-art.sh' script uses parallel directory information
+(without uncommon directory levels) to build the documentation entry
+required by Texinfo to store documentation entries inside the
+repository.
@@ -288,8 +287,8 @@ documentation inside the repository.
Othertimes, parallel directories may add uncommon information to their
-paths. This is the case of branches and tags creation. When we create
-branches and tags, a numerical identifier is added to parallel
+paths. This is the case we use to create branches and tags. When we
+create branches and tags, a numerical identifier is added to parallel
directory structure path. The place where the numerical identifier is
set on is relevant to corporate visual identity structure and should
be carefully considered where it will be.
@@ -319,26 +318,26 @@ initially created for.
3.39.2.5 Syncronizing path information
Creating parallel directories is very useful to keep repository
-organized, but what would happen to functionalities like help
+organized. But, what would happen to functionalities like help
(see section trunk/Scripts/Bash/Functions/Help) that rely on parent
directory structures to create documentation entries (using parallel
directory structures) if one of those parent directory structures
-suddenly change after the documentation entry has been already created
-for it?
+suddenly changes after the documentation entry has been already
+created for it?
Well, at this point, functionalities like help may confuse
-themselves if path information is not syncronized correctly. Such
-functionalities work with parent directory structure as reference; if
-a parent directory changes, the functionalities dont't even note it
-because they work with the last parent directory structure available
-in the repository, no matter what it is.
+themselves if path information is not updated. Such functionalities
+work with parent directory structure as reference; if a parent
+directory changes, the functionalities dont't even note it because
+they work with the last parent directory structure available in the
+repository, no matter what it is.
In the specific case of documentation (the help functionality),
the problem mentioned above provokes that older parent directories,
already documented, remain inside documentation directory structures
-in perpetuity, as long as you get your hands into the documentation
-directory structure (`trunk/Manuals') and remove what must be
-removed to match the new parent directory structure.
+as long as you get your hands into the documentation directory
+structure (`trunk/Manuals') and remove what must be removed to
+match the new parent directory structure.
There is no way for help, and similar functionalities that use
parent directories as reference, to know when and how directory
@@ -390,20 +389,21 @@ your own comprehension and so, make your propositions based on it.
When looking the correct place to store new files, to bear in mind the
corporate visual identity structure used inside the CentOS Artwork
Repository (see section trunk/Identity) would be probaly the best advice
-we could offer you, the rest is just matter of choosing appropriate
+we could offer to you, the rest is just matter of choosing appropriate
names. To illustrate this desition process let's consider the
`trunk/Identity/Themes/Motifs/TreeFlower/Distro/' directory as
example. It is the main development line of CentOS distribution visual
manifestation, using TreeFlower's artistic motif, inside themes of
-CentOS corporate visual identity structure.
+CentOS corporate visual identity.
When building parent directory structures, you may find that reaching
an acceptable location may take some time, and as it happens most of
-time, it is not a definite solution. There are many concepts that you
-need to play with, in order to find a result that match the conceptual
-idea you try to implement in the new directory location. To know which
-these concepts are, split the location in words and read its
-documentation entry from less specific to more specific.
+time, when you find it, that may be not a definite solution. There are
+many concepts that you need to play with, in order to find a result
+that match the conceptual idea you try to implement in the new
+directory location. To know which these concepts are, split the
+location in words and read its documentation entry from less specific
+to more specific.
For example, the
`trunk/Identity/Themes/Motifs/TreeFlower/Distro/' location
@@ -428,17 +428,103 @@ concepts for.
3.39.3 Usage
-
These commands are not available yet.
+
+-
centos-art path --copy='SRC DST'
+Use this command to duplicate `SRC' in working copy,
+remembering history. In this command, `SRC' and
+`DST' can each be either a working copy (WC) path or
+URL:
+
+
+- `WC -> WC'
+Copy and schedule for addition (with history).
+
+- `WC -> URL'
+Immediately commit a copy of WC to URL.
+
+- `URL -> WC'
+Check out URL into WC, schedule for addition.
+
+- `URL -> URL'
+Complete server-side copy; used to branch and tag.
+
+
+This command is an interface for Subversion's copy command.
+Options related to Subversion's copy command can be passed
+from third argument on. For example to specify a log message use the
+`--message' option as follow:
+
+centos-art path --copy='URL/SRC URL/DST' --message 'Copy url/src to url/dst'
+
+For more information on Subversion's copy functionality,
+run the command: svn help copy | less.
+
+-
centos-art path --move='SRC DST'
+Move and/or rename something in working copy or repository. In this
+command, SRC and DST can both be working copy (WC) paths or URLs:
+
+
+- `WC -> WC'
+Move and schedule for addition (with history).
+
- `URL -> URL'
+Complete server-side rename.
+
+
+This command is an interface for Subversion's move command.
+Options related to Subversion's move command can be passed
+from third argument on. For example to specify a log message use the
+`--message' option as follow:
+
+centos-art path --move='URL/SRC URL/DST' --message 'Move url/src to url/dst'
+
+For more information on Subversion's move functionality,
+run the command: svn help move | less.
+
+-
centos-art path --delete='SRC'
+Use this command to remove files and directories from version control.
+In this command, `SRC' can be a working copy (WC) path or URL.
--
centos-art path --sync='path/to/dir'
--
centos-art path --copy='path/to/oldfile path/to/newfile'
--
centos-art path --move='path/to/oldfile path/to/newfile'
-Move `path/to/oldfile' to `path/to/newfile'.
+
- `WC'
+Each item specified by a PATH is scheduled for deletion upon the next
+commit. Files, and directories that have not been committed, are
+immediately removed from the working copy. PATHs that are, or
+contain, unversioned or modified items will not be removed unless the
+`--force' option is given.
+
+- `URL'
+Each item specified by a URL is deleted from the repository via an
+immediate commit.
+
+
+This command is an interface for Subversion's delete
+command. Options related to Subversion's delete can be
+passed from third argument on. For example to specify a log message
+use the `--message' as follow:
+
+centos-art path --delete='URL' --message 'Delete url.'
+
+For more information on Subversion's delete functionality,
+run the command: svn help delete | less.
+
+-
centos-art path --sync='SRC'
+Use this command to syncronize path information inside working copy.
+This command is automatically used after moving or renaming parent
+directories. In this command, `SRC' is a working copy path
+inside `trunk/Identity/' location, considered the parent
+directory you want to syncronize path information for.
-
centos-art path --remove='path/to/file'
--
centos-art path --create-tag-from='path/to/dir'
--
centos-art path --create-branch-from='path/to/dir'
@@ -446,6 +532,8 @@ concepts for.
3.39.4 See also
diff --git a/Manuals/en/Info/Repository/repository.info.bz2 b/Manuals/en/Info/Repository/repository.info.bz2
index 4301d70..bf7fd56 100644
Binary files a/Manuals/en/Info/Repository/repository.info.bz2 and b/Manuals/en/Info/Repository/repository.info.bz2 differ
diff --git a/Manuals/en/Plaintext/Repository/repository.txt b/Manuals/en/Plaintext/Repository/repository.txt
index 67aabe1..a700ca2 100644
--- a/Manuals/en/Plaintext/Repository/repository.txt
+++ b/Manuals/en/Plaintext/Repository/repository.txt
@@ -3589,12 +3589,11 @@ Parallel directories are useful to create branches, tags, translations,
documentation, pre-rendering configuration script, and similar
directory structures.
- Parallel directory structures take their structure from one unique
-parent directory structure. Inside CentOS Artwork Repository, this
-unique parent directory structure is under `trunk/Identity' directory.
-The `trunk/Identity' directory structure must be considered the
-reference for whatever information you plan to create inside the
-repository.
+ Parallel directories take their structure from one unique parent
+directory. Inside CentOS Artwork Repository, this unique parent
+directory is under `trunk/Identity' location. The `trunk/Identity'
+location must be considered the reference for whatever information you
+plan to create inside the repository.
In some circumstances, parallel directories may be created removing
uncommon information from their paths. Uncommon path information refers
@@ -3606,18 +3605,17 @@ levels from path, in order to build the parallel directory used to
retrived translations, and pre-rendering configuration scripts required
by `render' functionality.
- Another example where parallel directory information is built by
-removing the uncommon path information is when we use the `help'
-functionality. This time, `centos-art.sh' script uses parallel
-directory information (without uncommon directory levels) to build the
-documentation entry required by Texinfo to store directory
-documentation inside the repository.
+ Another example where parallel directory removes the uncommon path
+information is when we use the `help' functionality. This time,
+`centos-art.sh' script uses parallel directory information (without
+uncommon directory levels) to build the documentation entry required by
+Texinfo to store documentation entries inside the repository.
Figure 3.4: Parallel directories removing uncommon information.
Othertimes, parallel directories may add uncommon information to
-their paths. This is the case of branches and tags creation. When we
-create branches and tags, a numerical identifier is added to parallel
+their paths. This is the case we use to create branches and tags. When
+we create branches and tags, a numerical identifier is added to parallel
directory structure path. The place where the numerical identifier is
set on is relevant to corporate visual identity structure and should be
carefully considered where it will be.
@@ -3638,25 +3636,25 @@ initially created for.
......................................
Creating parallel directories is very useful to keep repository
-organized, but what would happen to functionalities like `help' (*note
+organized. But, what would happen to functionalities like `help' (*note
trunk Scripts Bash Functions Help::) that rely on parent directory
structures to create documentation entries (using parallel directory
-structures) if one of those parent directory structures suddenly change
-after the documentation entry has been already created for it?
+structures) if one of those parent directory structures suddenly
+changes after the documentation entry has been already created for it?
Well, at this point, functionalities like `help' may confuse
-themselves if path information is not syncronized correctly. Such
-functionalities work with parent directory structure as reference; if a
-parent directory changes, the functionalities dont't even note it
-because they work with the last parent directory structure available in
-the repository, no matter what it is.
+themselves if path information is not updated. Such functionalities
+work with parent directory structure as reference; if a parent
+directory changes, the functionalities dont't even note it because they
+work with the last parent directory structure available in the
+repository, no matter what it is.
In the specific case of documentation (the `help' functionality),
the problem mentioned above provokes that older parent directories,
-already documented, remain inside documentation directory structures in
-perpetuity, as long as you get your hands into the documentation
-directory structure (`trunk/Manuals') and remove what must be removed
-to match the new parent directory structure.
+already documented, remain inside documentation directory structures as
+long as you get your hands into the documentation directory structure
+(`trunk/Manuals') and remove what must be removed to match the new
+parent directory structure.
There is no way for `help', and similar functionalities that use
parent directories as reference, to know when and how directory
@@ -3706,20 +3704,21 @@ own comprehension and so, make your propositions based on it.
When looking the correct place to store new files, to bear in mind
the corporate visual identity structure used inside the CentOS Artwork
Repository (*note trunk Identity::) would be probaly the best advice we
-could offer you, the rest is just matter of choosing appropriate names.
-To illustrate this desition process let's consider the
+could offer to you, the rest is just matter of choosing appropriate
+names. To illustrate this desition process let's consider the
`trunk/Identity/Themes/Motifs/TreeFlower/Distro/' directory as example.
It is the main development line of CentOS distribution visual
manifestation, using TreeFlower's artistic motif, inside themes of
-CentOS corporate visual identity structure.
+CentOS corporate visual identity.
When building parent directory structures, you may find that reaching
an acceptable location may take some time, and as it happens most of
-time, it is not a definite solution. There are many concepts that you
-need to play with, in order to find a result that match the conceptual
-idea you try to implement in the new directory location. To know which
-these concepts are, split the location in words and read its
-documentation entry from less specific to more specific.
+time, when you find it, that may be not a definite solution. There are
+many concepts that you need to play with, in order to find a result
+that match the conceptual idea you try to implement in the new
+directory location. To know which these concepts are, split the
+location in words and read its documentation entry from less specific
+to more specific.
For example, the `trunk/Identity/Themes/Motifs/TreeFlower/Distro/'
location evolved through several months of contant work and there is no
@@ -3743,20 +3742,88 @@ concepts for.
3.39.3 Usage
------------
-These commands are not available yet.
+`centos-art path --copy='SRC DST''
+ Use this command to duplicate `SRC' in working copy, remembering
+ history. In this command, `SRC' and `DST' can each be either a
+ working copy (WC) path or URL:
-`centos-art path --sync='path/to/dir''
+ `WC -> WC'
+ Copy and schedule for addition (with history).
-`centos-art path --copy='path/to/oldfile path/to/newfile''
+ `WC -> URL'
+ Immediately commit a copy of WC to URL.
-`centos-art path --move='path/to/oldfile path/to/newfile''
- Move `path/to/oldfile' to `path/to/newfile'.
+ `URL -> WC'
+ Check out URL into WC, schedule for addition.
-`centos-art path --remove='path/to/file''
+ `URL -> URL'
+ Complete server-side copy; used to branch and tag.
-`centos-art path --create-tag-from='path/to/dir''
+ This command is an interface for Subversion's `copy' command.
+ Options related to Subversion's `copy' command can be passed from
+ third argument on. For example to specify a log message use the
+ `--message' option as follow:
-`centos-art path --create-branch-from='path/to/dir''
+
+ centos-art path --copy='URL/SRC URL/DST' --message 'Copy url/src to url/dst'
+
+ For more information on Subversion's `copy' functionality, run the
+ command: `svn help copy | less'.
+
+`centos-art path --move='SRC DST''
+ Move and/or rename something in working copy or repository. In this
+ command, SRC and DST can both be working copy (WC) paths or URLs:
+
+ `WC -> WC'
+ Move and schedule for addition (with history).
+
+ `URL -> URL'
+ Complete server-side rename.
+
+ This command is an interface for Subversion's `move' command.
+ Options related to Subversion's `move' command can be passed from
+ third argument on. For example to specify a log message use the
+ `--message' option as follow:
+
+
+ centos-art path --move='URL/SRC URL/DST' --message 'Move url/src to url/dst'
+
+ For more information on Subversion's `move' functionality, run the
+ command: `svn help move | less'.
+
+`centos-art path --delete='SRC''
+ Use this command to remove files and directories from version
+ control. In this command, `SRC' can be a working copy (WC) path
+ or URL.
+
+ `WC'
+ Each item specified by a PATH is scheduled for deletion upon
+ the next commit. Files, and directories that have not been
+ committed, are immediately removed from the working copy.
+ PATHs that are, or contain, unversioned or modified items
+ will not be removed unless the `--force' option is given.
+
+ `URL'
+ Each item specified by a URL is deleted from the repository
+ via an immediate commit.
+
+ This command is an interface for Subversion's `delete' command.
+ Options related to Subversion's `delete' can be passed from third
+ argument on. For example to specify a log message use the
+ `--message' as follow:
+
+
+ centos-art path --delete='URL' --message 'Delete url.'
+
+ For more information on Subversion's `delete' functionality, run
+ the command: `svn help delete | less'.
+
+`centos-art path --sync='SRC''
+ Use this command to syncronize path information inside working
+ copy. This command is automatically used after moving or renaming
+ parent directories. In this command, `SRC' is a working copy path
+ inside `trunk/Identity/' location, considered the parent directory
+ you want to syncronize path information for.
3.39.4 See also
---------------
@@ -5579,24 +5646,24 @@ Index
*****
branches: See 1. (line 380)
-Common translation files: See 3.48.2.5. (line 5008)
-How to render brands' translation files: See 3.50.3. (line 5312)
-How to render fonts' translation files: See 3.52.3. (line 5385)
-How to render translation files: See 3.48.3. (line 5178)
-Metadata maintainance: See 3.43.2. (line 4152)
-Specific translation files: See 3.48.2.6. (line 5033)
+Common translation files: See 3.48.2.5. (line 5075)
+How to render brands' translation files: See 3.50.3. (line 5379)
+How to render fonts' translation files: See 3.52.3. (line 5452)
+How to render translation files: See 3.48.3. (line 5245)
+Metadata maintainance: See 3.43.2. (line 4219)
+Specific translation files: See 3.48.2.6. (line 5100)
tags: See 2. (line 383)
-Template translation files: See 3.48.2.4. (line 4838)
-Translation brands file names: See 3.50.2.1. (line 5269)
-Translation configuration scripts: See 3.48.2.8. (line 5067)
-Translation entries: See 3.48.2.1. (line 4654)
-Translation files: See 3.48.2.3. (line 4770)
-Translation markers: See 3.48.2.2. (line 4735)
-Translation paths: See 3.48.2.1. (line 4654)
+Template translation files: See 3.48.2.4. (line 4905)
+Translation brands file names: See 3.50.2.1. (line 5336)
+Translation configuration scripts: See 3.48.2.8. (line 5134)
+Translation entries: See 3.48.2.1. (line 4721)
+Translation files: See 3.48.2.3. (line 4837)
+Translation markers: See 3.48.2.2. (line 4802)
+Translation paths: See 3.48.2.1. (line 4721)
Translation pre-rendering configuration scripts:See 3.48.2.8.
- (line 5067)
-Translation rendering: See 3.48.2.7. (line 5056)
-Translation rendering default functionality: See 3.48.2.9. (line 5153)
+ (line 5134)
+Translation rendering: See 3.48.2.7. (line 5123)
+Translation rendering default functionality: See 3.48.2.9. (line 5220)
trunk: See 3. (line 386)
trunk Identity: See 3.1. (line 389)
trunk Identity Brands: See 3.2. (line 809)
@@ -5643,27 +5710,27 @@ trunk Scripts Bash Functions Help: See 3.36. (line 3281)
trunk Scripts Bash Functions Html: See 3.37. (line 3332)
trunk Scripts Bash Functions Locale: See 3.38. (line 3353)
trunk Scripts Bash Functions Path: See 3.39. (line 3433)
-trunk Scripts Bash Functions Render: See 3.40. (line 3767)
-trunk Scripts Bash Functions Render Config: See 3.41. (line 3788)
-trunk Scripts Bash Functions Shell: See 3.42. (line 3966)
-trunk Scripts Bash Functions Svg: See 3.43. (line 4134)
-trunk Scripts Bash Functions Verify: See 3.44. (line 4322)
-trunk Scripts Bash Locale: See 3.45. (line 4538)
-trunk Scripts Perl: See 3.46. (line 4567)
-trunk Scripts Python: See 3.47. (line 4584)
-trunk Translations: See 3.48. (line 4605)
-trunk Translations Identity: See 3.49. (line 5207)
-trunk Translations Identity Brands: See 3.50. (line 5228)
-trunk Translations Identity Brands Tpl: See 3.51. (line 5323)
-trunk Translations Identity Fonts: See 3.52. (line 5338)
-trunk Translations Identity Models: See 3.53. (line 5401)
-trunk Translations Identity Release: See 3.54. (line 5416)
-trunk Translations Identity Themes: See 3.55. (line 5431)
-trunk Translations Identity Themes Backgrounds:See 3.56. (line 5446)
+trunk Scripts Bash Functions Render: See 3.40. (line 3834)
+trunk Scripts Bash Functions Render Config: See 3.41. (line 3855)
+trunk Scripts Bash Functions Shell: See 3.42. (line 4033)
+trunk Scripts Bash Functions Svg: See 3.43. (line 4201)
+trunk Scripts Bash Functions Verify: See 3.44. (line 4389)
+trunk Scripts Bash Locale: See 3.45. (line 4605)
+trunk Scripts Perl: See 3.46. (line 4634)
+trunk Scripts Python: See 3.47. (line 4651)
+trunk Translations: See 3.48. (line 4672)
+trunk Translations Identity: See 3.49. (line 5274)
+trunk Translations Identity Brands: See 3.50. (line 5295)
+trunk Translations Identity Brands Tpl: See 3.51. (line 5390)
+trunk Translations Identity Fonts: See 3.52. (line 5405)
+trunk Translations Identity Models: See 3.53. (line 5468)
+trunk Translations Identity Release: See 3.54. (line 5483)
+trunk Translations Identity Themes: See 3.55. (line 5498)
+trunk Translations Identity Themes Backgrounds:See 3.56. (line 5513)
trunk Translations Identity Themes Distro Anaconda Progress:See 3.57.
- (line 5467)
-trunk Translations Identity Widgets: See 3.58. (line 5560)
-Unused definitions: See 3.43.2.1. (line 4259)
+ (line 5534)
+trunk Translations Identity Widgets: See 3.58. (line 5627)
+Unused definitions: See 3.43.2.1. (line 4326)
List of Figures
***************
diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Path.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Path.texi
index 174380f..71595c4 100644
--- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Path.texi
+++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Path.texi
@@ -162,12 +162,11 @@ Parallel directories are useful to create branches, tags,
translations, documentation, pre-rendering configuration script, and
similar directory structures.
-Parallel directory structures take their structure from one unique
-parent directory structure. Inside CentOS Artwork Repository, this
-unique parent directory structure is under @file{trunk/Identity}
-directory. The @file{trunk/Identity} directory structure must be
-considered the reference for whatever information you plan to create
-inside the repository.
+Parallel directories take their structure from one unique parent
+directory. Inside CentOS Artwork Repository, this unique parent
+directory is under @file{trunk/Identity} location. The
+@file{trunk/Identity} location must be considered the reference for
+whatever information you plan to create inside the repository.
In some circumstances, parallel directories may be created removing
uncommon information from their paths. Uncommon path information
@@ -180,12 +179,12 @@ build the parallel directory used to retrived translations, and
pre-rendering configuration scripts required by @code{render}
functionality.
-Another example where parallel directory information is built by
-removing the uncommon path information is when we use the @code{help}
-functionality. This time, @file{centos-art.sh} script uses parallel
-directory information (without uncommon directory levels) to build the
-documentation entry required by Texinfo to store directory
-documentation inside the repository.
+Another example where parallel directory removes the uncommon path
+information is when we use the @code{help} functionality. This time,
+@file{centos-art.sh} script uses parallel directory information
+(without uncommon directory levels) to build the documentation entry
+required by Texinfo to store documentation entries inside the
+repository.
@float Figure, trunk/Identity/Models/Img/Scripts/Bash/Functions/Paths/figure-3
@image{trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-3}
@@ -193,8 +192,8 @@ documentation inside the repository.
@end float
Othertimes, parallel directories may add uncommon information to their
-paths. This is the case of branches and tags creation. When we create
-branches and tags, a numerical identifier is added to parallel
+paths. This is the case we use to create branches and tags. When we
+create branches and tags, a numerical identifier is added to parallel
directory structure path. The place where the numerical identifier is
set on is relevant to corporate visual identity structure and should
be carefully considered where it will be.
@@ -220,26 +219,26 @@ initially created for.
@subsubsection Syncronizing path information
Creating parallel directories is very useful to keep repository
-organized, but what would happen to functionalities like @code{help}
+organized. But, what would happen to functionalities like @code{help}
(@pxref{trunk Scripts Bash Functions Help}) that rely on parent
directory structures to create documentation entries (using parallel
directory structures) if one of those parent directory structures
-suddenly change after the documentation entry has been already created
-for it?
+suddenly changes after the documentation entry has been already
+created for it?
Well, at this point, functionalities like @code{help} may confuse
-themselves if path information is not syncronized correctly. Such
-functionalities work with parent directory structure as reference; if
-a parent directory changes, the functionalities dont't even note it
-because they work with the last parent directory structure available
-in the repository, no matter what it is.
+themselves if path information is not updated. Such functionalities
+work with parent directory structure as reference; if a parent
+directory changes, the functionalities dont't even note it because
+they work with the last parent directory structure available in the
+repository, no matter what it is.
In the specific case of documentation (the @code{help} functionality),
the problem mentioned above provokes that older parent directories,
already documented, remain inside documentation directory structures
-in perpetuity, as long as you get your hands into the documentation
-directory structure (@file{trunk/Manuals}) and remove what must be
-removed to match the new parent directory structure.
+as long as you get your hands into the documentation directory
+structure (@file{trunk/Manuals}) and remove what must be removed to
+match the new parent directory structure.
There is no way for @code{help}, and similar functionalities that use
parent directories as reference, to know when and how directory
@@ -289,20 +288,21 @@ your own comprehension and so, make your propositions based on it.
When looking the correct place to store new files, to bear in mind the
corporate visual identity structure used inside the CentOS Artwork
Repository (@pxref{trunk Identity}) would be probaly the best advice
-we could offer you, the rest is just matter of choosing appropriate
+we could offer to you, the rest is just matter of choosing appropriate
names. To illustrate this desition process let's consider the
@file{trunk/Identity/Themes/Motifs/TreeFlower/Distro/} directory as
example. It is the main development line of CentOS distribution visual
manifestation, using TreeFlower's artistic motif, inside themes of
-CentOS corporate visual identity structure.
+CentOS corporate visual identity.
When building parent directory structures, you may find that reaching
an acceptable location may take some time, and as it happens most of
-time, it is not a definite solution. There are many concepts that you
-need to play with, in order to find a result that match the conceptual
-idea you try to implement in the new directory location. To know which
-these concepts are, split the location in words and read its
-documentation entry from less specific to more specific.
+time, when you find it, that may be not a definite solution. There are
+many concepts that you need to play with, in order to find a result
+that match the conceptual idea you try to implement in the new
+directory location. To know which these concepts are, split the
+location in words and read its documentation entry from less specific
+to more specific.
For example, the
@file{trunk/Identity/Themes/Motifs/TreeFlower/Distro/} location
@@ -327,20 +327,102 @@ concepts for.
@subsection Usage
-These commands are not available yet.
-
@table @command
-@item centos-art path --sync='path/to/dir'
-@item centos-art path --copy='path/to/oldfile path/to/newfile'
-@item centos-art path --move='path/to/oldfile path/to/newfile'
-Move @samp{path/to/oldfile} to @samp{path/to/newfile}.
-@item centos-art path --remove='path/to/file'
-@item centos-art path --create-tag-from='path/to/dir'
-@item centos-art path --create-branch-from='path/to/dir'
+@item centos-art path --copy='SRC DST'
+Use this command to duplicate @file{SRC} in working copy,
+remembering history. In this command, @file{SRC} and
+@file{DST} can each be either a working copy (WC) path or
+URL:
+
+@table @samp
+@item WC -> WC
+Copy and schedule for addition (with history).
+
+@item WC -> URL
+Immediately commit a copy of WC to URL.
+
+@item URL -> WC
+Check out URL into WC, schedule for addition.
+
+@item URL -> URL
+Complete server-side copy; used to branch and tag.
+@end table
+
+This command is an interface for Subversion's @command{copy} command.
+Options related to Subversion's @command{copy} command can be passed
+from third argument on. For example to specify a log message use the
+@option{--message} option as follow:
+
+@verbatim
+centos-art path --copy='URL/SRC URL/DST' --message 'Copy url/src to url/dst'
+@end verbatim
+
+For more information on Subversion's @command{copy} functionality,
+run the command: @command{svn help copy | less}.
+
+@item centos-art path --move='SRC DST'
+Move and/or rename something in working copy or repository. In this
+command, SRC and DST can both be working copy (WC) paths or URLs:
+
+@table @samp
+@item WC -> WC
+Move and schedule for addition (with history).
+@item URL -> URL
+Complete server-side rename.
+@end table
+
+This command is an interface for Subversion's @command{move} command.
+Options related to Subversion's @command{move} command can be passed
+from third argument on. For example to specify a log message use the
+@option{--message} option as follow:
+
+@verbatim
+centos-art path --move='URL/SRC URL/DST' --message 'Move url/src to url/dst'
+@end verbatim
+
+For more information on Subversion's @command{move} functionality,
+run the command: @command{svn help move | less}.
+
+@item centos-art path --delete='SRC'
+Use this command to remove files and directories from version control.
+In this command, @file{SRC} can be a working copy (WC) path or URL.
+
+@table @samp
+@item WC
+Each item specified by a PATH is scheduled for deletion upon the next
+commit. Files, and directories that have not been committed, are
+immediately removed from the working copy. PATHs that are, or
+contain, unversioned or modified items will not be removed unless the
+@option{--force} option is given.
+
+@item URL
+Each item specified by a URL is deleted from the repository via an
+immediate commit.
+@end table
+
+This command is an interface for Subversion's @command{delete}
+command. Options related to Subversion's @command{delete} can be
+passed from third argument on. For example to specify a log message
+use the @option{--message} as follow:
+
+@verbatim
+centos-art path --delete='URL' --message 'Delete url.'
+@end verbatim
+
+For more information on Subversion's @command{delete} functionality,
+run the command: @command{svn help delete | less}.
+
+@item centos-art path --sync='SRC'
+Use this command to syncronize path information inside working copy.
+This command is automatically used after moving or renaming parent
+directories. In this command, @file{SRC} is a working copy path
+inside @file{trunk/Identity/} location, considered the parent
+directory you want to syncronize path information for.
@end table
@subsection See also
@menu
+* trunk Scripts Bash::
* trunk Scripts Bash Functions::
@end menu