Blame Manuals/en/Html/Repository/repository_43.html

4c79b5
4c79b5
<html>
09d4f2
09d4f2
09d4f2
The CentOS Artwork Repository exists to organize and automate The
09d4f2
CentOS Project corporate visual identity (, to
09d4f2
start on).
4c79b5
6c4982
Copyright C 2009, 2010 Alain Reguera Delgado. All rights
4c79b5
reserved.
4c79b5
4c79b5
Permission is granted to copy, distribute and/or modify this document
4c79b5
under the terms of the GNU Free Documentation License, Version 1.2 or
4c79b5
any later version published by the Free Software Foundation; with no
4c79b5
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
4c79b5
copy of the license is included in the section entitled GNU Free
4c79b5
Documentation License.  
4c79b5
-->
008ee0
4c79b5
4c79b5
Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
4c79b5
            Karl Berry  <karl@freefriends.org>
4c79b5
            Olaf Bachmann <obachman@mathematik.uni-kl.de>
4c79b5
            and many others.
4c79b5
Maintained by: Many creative people <dev@texi2html.cvshome.org>
4c79b5
Send bugs and suggestions to <users@texi2html.cvshome.org>
4c79b5
4c79b5
-->
4c79b5
<head>
e68a7a
<title>CentOS Artwork Repository: 3.40 trunk/Scripts/Bash/Functions/Path</title>
4c79b5
e68a7a
<meta name="description" content="CentOS Artwork Repository: 3.40 trunk/Scripts/Bash/Functions/Path">
e68a7a
<meta name="keywords" content="CentOS Artwork Repository: 3.40 trunk/Scripts/Bash/Functions/Path">
4c79b5
<meta name="resource-type" content="document">
4c79b5
<meta name="distribution" content="global">
4c79b5
<meta name="Generator" content="texi2html 1.76">
4c79b5
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
4c79b5
<style type="text/css">
4c79b5
1e9202
@import "/home/centos/artwork/trunk/Identity/Models/Css/Texi2html/common.css";
4c79b5
4c79b5
a.summary-letter {text-decoration: none}
4c79b5
pre.display {font-family: serif}
4c79b5
pre.format {font-family: serif}
4c79b5
pre.menu-comment {font-family: serif}
4c79b5
pre.menu-preformatted {font-family: serif}
4c79b5
pre.smalldisplay {font-family: serif; font-size: smaller}
4c79b5
pre.smallexample {font-size: smaller}
4c79b5
pre.smallformat {font-family: serif; font-size: smaller}
4c79b5
pre.smalllisp {font-size: smaller}
4c79b5
span.sansserif {font-family:sans-serif; font-weight:normal;}
4c79b5
ul.toc {list-style: none}
4c79b5
-->
4c79b5
</style>
4c79b5
4c79b5
4c79b5
</head>
4c79b5
4c79b5
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
4c79b5
4c79b5
cbf5a9
[ < ]
cbf5a9
[ > ]
4c79b5
   
4c79b5
[ << ]
4c79b5
[ Up ]
e68a7a
[ >> ]
4c79b5
   
4c79b5
   
4c79b5
   
4c79b5
   
4c79b5
[Top]
4c79b5
[Contents]
e68a7a
[Index]
4c79b5
[ ? ]
4c79b5
e68a7a
cbf5a9
e68a7a

3.40 trunk/Scripts/Bash/Functions/Path

6aec21
008ee0
cbf5a9
63f275

3.40.1 Goals

008ee0
e68a7a

This section exists to organize files related to path

e68a7a
functiontionality of <tt>`centos-art.sh'</tt> script.  The path
e68a7a
functionality of <tt>`centos-art.sh'</tt> script standardizes movement,
e68a7a
syncronization, branching, tagging, and general file maintainance
e68a7a
inside the repository. 
e68a7a

008ee0
cbf5a9
63f275

3.40.2 Description

63f275
e68a7a

"CentOS like trees, has roots, trunk, branches, leaves and

e68a7a
flowers.  Day by day they work together in freedom, ruled by the laws
e68a7a
of nature and open standards, to show the beauty of its
e68a7a
existence."
e68a7a

008ee0
cbf5a9
e68a7a

3.40.2.1 Repository layout

e68a7a
e68a7a

The repository layout describes organization of files and directories

e68a7a
inside the repository. The repository layout provides the standard
e68a7a
backend required for automation scripts to work correctly. If such
e68a7a
layout changes unexpectedly, automation scripts may confuse themselves
e68a7a
and stop doing what we expect from them to do.
e68a7a

e68a7a

As convenction, inside CentOS Artwork Repository, we organize files

e68a7a
and directories, related to CentOS corporate visual identity, under
e68a7a
three top level directories named <tt>`trunk/'</tt>, <tt>`branches/'</tt>, and
e68a7a
<tt>`tags/'</tt>. 
e68a7a

e68a7a
e68a7a

trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-6

e68a7a
e68a7a

Figure 3.10: The CentOS Artwork Repository layout.

e68a7a
e68a7a

e68a7a

The <tt>`trunk/'</tt> directory (see section trunk) organizes the main

e68a7a
development line of CentOS corporate visual identity. Inside
e68a7a
<tt>`trunk/'</tt> directory structure, the CentOS corporate visual
e68a7a
identity concepts are implemented using directories.  There is one
e68a7a
directory level for each relevant concept inside the repository. The
e68a7a
<tt>`trunk/'</tt> directory structure is mainly used to develop CentOS
e68a7a
corporate visual identity.
e68a7a

e68a7a

The <tt>`branches/'</tt> directory (see section branches) oranizes parallel

e68a7a
development lines to <tt>`trunk/'</tt> directory. The <tt>`branches/'</tt>
e68a7a
directory is used to set points in time where develpment lines are
e68a7a
devided one from another taking separte and idependent lives that
e68a7a
share a common past from the point they were devided on. The
e68a7a
<tt>`branches/'</tt> directory is mainly used to perform quality assurance
e68a7a
on CentOS corporate visual identity.
e68a7a

e68a7a

The <tt>`tags/'</tt> directory (see section tags) organizes parallel frozen

e68a7a
lines to <tt>`branches/'</tt> directory.  The parallel frozen lines are
e68a7a
immutable, nothing change inside them once they has been created.  The
e68a7a
<tt>`tags/'</tt> directory is mainly used to publish final releases of
e68a7a
CentOS corporate visual identity.
e68a7a

e68a7a

The CentOS Artwork Repository layout is firmly grounded on a

e68a7a
Subversion base.  Subversion (http://subversion.tigris.org) is a
e68a7a
version control system, which allows you to keep old versions of files
e68a7a
and directories (usually source code), keep a log of who, when, and
e68a7a
why changes occurred, etc., like CVS, RCS or SCCS.  Subversion keeps a
e68a7a
single copy of the master sources.  This copy  is called the source
e68a7a
"repository"; it contains all the information to permit extracting
e68a7a
previous versions of those files at any time.
e68a7a

e68a7a
e68a7a
e68a7a

3.40.2.2 Repository name convenctions

e68a7a
e68a7a

Repository name convenctions help us to maintain consistency of names

e68a7a
inside the repository.
e68a7a

e68a7a

Repository name convenctions are applied to files and directories

e68a7a
inside the repository layout. As convenction, inside the repository
e68a7a
layout, file names are all written in lowercase
e68a7a
(<samp>`01-welcome.png'</samp>, <samp>`splash.png'</samp>, <samp>`anaconda_header.png'</samp>,
e68a7a
etc.) and directory names are all written capitalized (e.g.,
e68a7a
<samp>`Identity'</samp>, <samp>`Themes'</samp>, <samp>`Motifs'</samp>, <samp>`TreeFlower'</samp>,
e68a7a
etc.).
e68a7a

e68a7a

Repository name convenctions are implemented inside the

e68a7a
cli_getRepoName function of <tt>`centos-art.sh'</tt> script. With
e68a7a
cli_getRepoName function we reduce the amount of commands and
e68a7a
convenctions you need to remember concentrating them in just one
e68a7a
single place you can look for fixes and improvements.
e68a7a

e68a7a
e68a7a
e68a7a

3.40.2.3 Repository work flow

e68a7a
e68a7a

Repository work flow describes the steps and time intervals used to

e68a7a
produce CentOS corporate visual identity inside CentOS Artwork
e68a7a
Repository.  
e68a7a

e68a7a

To illustrate repository work flow let's consider themes' development

e68a7a
cycle. 
e68a7a

e68a7a

Initially, we start working themes on their trunk development line

e68a7a
(e.g., <tt>`trunk/Identity/Themes/Motifs/TreeFlower/'</tt>), here we
e68a7a
design background images and propagate them to different visual
e68a7a
manifestations using one theme's model as reference.
e68a7a

e68a7a

Later, when the theme is considered "ready" for implementation (i.e.

e68a7a
all visual manifestations have been already set), we create a branch
e68a7a
for it (e.g., <tt>`branches/Identity/Themes/Motifs/TreeFlower/1/'</tt>).
e68a7a
Once the branch has been created, we forget that branch and continue
e68a7a
working the trunk development line while others (e.g., an artwork
e68a7a
quality assurance team) test the new branch for tunning it up. 
e68a7a

e68a7a

Once the branch has been tunned up, and considered "ready" for

e68a7a
release, it is freezed under <tt>`tags/'</tt> directory (e.g.,
e68a7a
<tt>`tags/Identity/Themes/Motifs/TreeFower/1.0/'</tt>) for packagers,
e68a7a
webmasters, promoters, and anyone who needs images from that CentOS
e68a7a
theme the tag was created for.
e68a7a

e68a7a

Both branches and tags, inside CentOS Artwork Repository, use

e68a7a
numerical values to identify themselves under the same location.
e68a7a
Branches start at one (i.e., <samp>`1'</samp>) and increment one unit for each
e68a7a
branch created from the same trunk development line.  Tags start at
e68a7a
zero (i.e., <samp>`0'</samp>) and increment one unit for each tag created from
e68a7a
the same branch development line.
e68a7a

e68a7a
e68a7a

trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-1

e68a7a
e68a7a

Figure 3.11: Name convention for tags and branches creation.

e68a7a
e68a7a

e68a7a

As proposition, it would be convenient not to freeze trunk development

e68a7a
lines using tags or anything else.  If you think you need to freeze a
e68a7a
trunk development line, create a branch for it and then freeze that
e68a7a
branch instead.  
e68a7a

e68a7a

The trunk development line may introduce problems we cannot see

e68a7a
immediatly. Certainly, the high changable nature of trunk development
e68a7a
line complicates finding and fixing such problems. On the other hand,
e68a7a
the branched development lines provides a less changable area where
e68a7a
only small fixes/corrections are commited up to repository. 
e68a7a

e68a7a

If others find and fix bugs inside the branched development line, we

e68a7a
could merge such changes/experiences back to trunk development line
e68a7a
(not visversa) in order for future branches, created from trunk, to
e68a7a
benefit.
e68a7a

e68a7a

Time intervals used to create branches and tags may vary, just as

e68a7a
different needs may arrive. For example, consider the release schema
e68a7a
of CentOS distribution: one major release every 2 years, security
e68a7a
updates every 6 months, support for 7 years long. Each time a CentOS
e68a7a
distribution is released, specially if it is a major release, there is
e68a7a
a theme need in order to cover CentOS distribution artwork
e68a7a
requirements. At this point, is where CentOS Artwork Repository comes
e68a7a
up to scene. 
e68a7a

e68a7a

Before releasing a new major release of CentOS distribution you can

e68a7a
create a branch for one of several theme development lines available
e68a7a
inside the CentOS Artwork Repository, perform quality assurance on it,
e68a7a
and later, freeze that branch using tags. Once a the theme branch has
e68a7a
been frozen (under <tt>`tags/'</tt> directory), CentOS Packagers (the
e68a7a
persons who build CentOS distribution) can use that frozen branch as
e68a7a
source location to fulfill CentOS distribution artwork needs.
e68a7a

e68a7a
e68a7a
e68a7a

3.40.2.4 Parallel directories

e68a7a
e68a7a

Inside CentOS Artwork Repository, parallel directories are simple

e68a7a
directory entries built from a common parent directory and placed in a
e68a7a
location different to that, the common parent directory is placed on.
e68a7a
Parallel directories are useful to create branches, tags,
e68a7a
translations, documentation, pre-rendering configuration script, and
e68a7a
similar directory structures.
e68a7a

e68a7a

Parallel directories take their structure from one unique parent

e68a7a
directory. Inside CentOS Artwork Repository, this unique parent
e68a7a
directory is under <tt>`trunk/Identity'</tt> location.  The
e68a7a
<tt>`trunk/Identity'</tt> location must be considered the reference for
e68a7a
whatever information you plan to create inside the repository.
e68a7a

e68a7a

In some circumstances, parallel directories may be created removing

e68a7a
uncommon information from their paths. Uncommon path information
e68a7a
refers to those directory levels in the path which are not common for
e68a7a
other parallel directories.  For example, when rendering
e68a7a
<tt>`trunk/Identity/Themes/Motifs/TreeFlower/Distro'</tt> directory
e68a7a
structure, the <tt>`centos-art.sh'</tt> script removes the
e68a7a
<tt>`Motifs/TreeFlower/'</tt> directory levels from path, in order to
e68a7a
build the parallel directory used to retrived translations, and
e68a7a
pre-rendering configuration scripts required by render
e68a7a
functionality.
e68a7a

e68a7a

Another example where parallel directory removes the uncommon path

e68a7a
information is when we use the help functionality. This time,
e68a7a
<tt>`centos-art.sh'</tt> script uses parallel directory information
e68a7a
(without uncommon directory levels) to build the documentation entry
e68a7a
required by Texinfo to store documentation entries inside the
e68a7a
repository.
e68a7a

e68a7a
e68a7a

trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-3

e68a7a
e68a7a

Figure 3.12: Parallel directories removing uncommon information.

e68a7a
e68a7a

e68a7a

Othertimes, parallel directories may add uncommon information to their

e68a7a
paths. This is the case we use to create branches and tags. When we
e68a7a
create branches and tags, a numerical identifier is added to parallel
e68a7a
directory structure path. The place where the numerical identifier is
e68a7a
set on is relevant to corporate visual identity structure and should
e68a7a
be carefully considered where it will be.
e68a7a

e68a7a
e68a7a

trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-4

e68a7a
e68a7a

Figure 3.13: Parallel directories adding uncommon information.

e68a7a
e68a7a

e68a7a

When one parent directory changes, all their related parallel

e68a7a
directories need to be changed too. This is required in order for
e68a7a
parallel directories to match the new parent directory structure.  In
e68a7a
the other hand, parallel directories should never be modified by no
e68a7a
reason but to satisfy their parent directory structure. Liberal change
e68a7a
of parallel directories may suppress the conceptual idea they were
e68a7a
initially created for.
e68a7a

e68a7a
e68a7a

trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-5

e68a7a
e68a7a

Figure 3.14: Wrong construction of parallel directories.

e68a7a
e68a7a

e68a7a
e68a7a
e68a7a

3.40.2.5 Syncronizing path information

e68a7a
e68a7a

Creating parallel directories is very useful to keep repository

e68a7a
organized. But, what would happen to functionalities like help
e68a7a
(WARNING: The <samp>`trunk Scripts Bash Functions Help'</samp> documentation entry no longer exists.) that rely on parent
e68a7a
directory structures to create documentation entries (using parallel
e68a7a
directory structures) if one of those parent directory structures
e68a7a
suddenly changes after the documentation entry has been already
e68a7a
created for it? 
e68a7a

e68a7a

Well, at this point, functionalities like help may confuse

e68a7a
themselves if path information is not updated.  Such functionalities
e68a7a
work with parent directory structure as reference; if a parent
e68a7a
directory changes, the functionalities dont't even note it because
e68a7a
they work with the last parent directory structure available in the
e68a7a
repository, no matter what it is. 
e68a7a

e68a7a

In the specific case of documentation (the help functionality),

e68a7a
the problem mentioned above provokes that older parent directories,
e68a7a
already documented, remain inside documentation directory structures
e68a7a
as long as you get your hands into the documentation directory
e68a7a
structure (<tt>`trunk/Manuals'</tt>) and remove what must be removed to
e68a7a
match the new parent directory structure.
e68a7a

e68a7a

There is no way for help, and similar functionalities that use

e68a7a
parent directories as reference, to know when and how directory
e68a7a
movements take place inside the repository. Such information is
e68a7a
available only when movement actions, like thoses achived by
e68a7a
rm or mv commands, take place inside the
e68a7a
repository. So, is there, at the moment of moving files, when we need
e68a7a
to syncronize parallel directories with their unique parent directory
e68a7a
structure.
e68a7a

e68a7a

Syncronizing parallel directories with their respecitive parent

e68a7a
directory implies moving files inside the repository, i.e. we need to,
e68a7a
firstly, rebuild the path information for each parallel directory
e68a7a
inside the repository, using the current path of its parent directory
e68a7a
as reference, and later, use the new path information to move each old
e68a7a
parallel directory from its old location to its new location based on
e68a7a
an updated path information.
e68a7a

e68a7a

As CentOS Artwork Repository is built over a version control system,

e68a7a
file movements inside the repository are considered repository
e68a7a
changes. In order for these repository changes to be versioned, we
e68a7a
need to, firstly, add changes related files into version control
e68a7a
system, and later, use commands from the version control system to
e68a7a
move those files already versioned.  This configuration makes possible
e68a7a
for everyone to know about changes details inside the repository; and
e68a7a
if needed, revert or update them back to a previous revision.
e68a7a

e68a7a

Finally, once all file corrections have been already made, the

e68a7a
syncronization action takes care of updating path references inside
e68a7a
related files. Updating path references inside related files is
e68a7a
specially important for documentation files where documentation nodes
e68a7a
are built using repository path information as reference.
e68a7a

e68a7a
e68a7a
e68a7a

3.40.2.6 What is the right location to store it?

e68a7a
e68a7a

Occasionly, you may find that new corporate visual identity components

e68a7a
need to be added to the repository. If that is your case, the first
e68a7a
question you need to ask yourself, before start to create directories
e68a7a
blindly all over, is: What is the right location to store it?
e68a7a

e68a7a

The CentOS Community (http://wiki.centos.org/GettingHelp) is the

e68a7a
best place to find answers to your question, but going there with
e68a7a
hands empty is not good idea. It may give the impression you don't
e68a7a
really care about. Instead, consider the following suggestions to find
e68a7a
your own comprehension and so, make your propositions based on it.
e68a7a

e68a7a

When looking the correct place to store new files, to bear in mind the

e68a7a
corporate visual identity structure used inside the CentOS Artwork
e68a7a
Repository (see section trunk/Identity) would be probaly the best advice
e68a7a
we could offer to you, the rest is just matter of choosing appropriate
e68a7a
names.  To illustrate this desition process let's consider the
e68a7a
<tt>`trunk/Identity/Themes/Motifs/TreeFlower/Distro/'</tt> directory as
e68a7a
example. It is the main development line of CentOS distribution visual
e68a7a
manifestation, using TreeFlower's artistic motif, inside themes of
e68a7a
CentOS corporate visual identity. 
e68a7a

e68a7a

When building parent directory structures, you may find that reaching

e68a7a
an acceptable location may take some time, and as it happens most of
e68a7a
time, when you find it, that may be not a definite solution. There are
e68a7a
many concepts that you need to play with, in order to find a result
e68a7a
that match the conceptual idea you try to implement in the new
e68a7a
directory location. To know which these concepts are, split the
e68a7a
location in words and read its documentation entry from less specific
e68a7a
to more specific.
e68a7a

e68a7a

For example, the

e68a7a
<tt>`trunk/Identity/Themes/Motifs/TreeFlower/Distro/'</tt> location
e68a7a
evolved through several months of contant work and there is no certain
e68a7a
it won't change in the future, even it fixes quite well the concept we
e68a7a
are trying to implement.  The concepts used in
e68a7a
<tt>`trunk/Identity/Themes/Distro/Motifs/TreeFlower/Distro/'</tt> location
e68a7a
are described in the following commands, respectively:
e68a7a

e68a7a
centos-art help --read=turnk/
e68a7a
centos-art help --read=turnk/Identity/
e68a7a
centos-art help --read=turnk/Identity/Themes/
e68a7a
centos-art help --read=turnk/Identity/Themes/Motifs/
e68a7a
centos-art help --read=turnk/Identity/Themes/Motifs/TreeFlower/
e68a7a
centos-art help --read=turnk/Identity/Themes/Motifs/TreeFlower/Distro/
e68a7a
e68a7a

Other location concepts can be found similary as we did above, just

e68a7a
change the location we used above by the one you are trying to know
e68a7a
concepts for.
e68a7a

e68a7a
e68a7a
63f275

3.40.3 Usage

63f275
63f275
e68a7a
centos-art path --copy=SRC --to=DST
e68a7a

Use this command to duplicate <tt>`SRC'</tt> in working copy,

e68a7a
remembering history. In this command, <tt>`SRC'</tt> and
e68a7a
<tt>`DST'</tt> can each be either a working copy (WC) path or
e68a7a
URL:
e68a7a

e68a7a
e68a7a
<samp>`WC -> WC'</samp>
e68a7a

Copy and schedule for addition (with history).

e68a7a

e68a7a
e68a7a
<samp>`WC -> URL'</samp>
e68a7a

Immediately commit a copy of WC to URL.

e68a7a

e68a7a
e68a7a
<samp>`URL -> WC'</samp>
e68a7a

Check out URL into WC, schedule for addition.

e68a7a

e68a7a
e68a7a
<samp>`URL -> URL'</samp>
e68a7a

Complete server-side copy; used to branch and tag.

e68a7a

e68a7a
e68a7a
e68a7a

This command is an interface for Subversion's copy command.

e68a7a
Options related to Subversion's copy command can be passed
e68a7a
from third argument on. For example to specify a log message use the
e68a7a
<samp>`--message'</samp> option as follow:
e68a7a

e68a7a
centos-art path --copy=URL/SRC --to=URL/DST --message 'Copy url/src to url/dst'
e68a7a
e68a7a

For more information on Subversion's copy functionality,

e68a7a
run the command: svn help copy | less.
e68a7a

e68a7a
e68a7a
centos-art path --move=SRC --to=DST
e68a7a

Move and/or rename something in working copy or repository. In this

e68a7a
command, SRC and DST can both be working copy (WC) paths or URLs: 
e68a7a

e68a7a
e68a7a
<samp>`WC -> WC'</samp>
e68a7a

Move and schedule for addition (with history).

63f275

e68a7a
<samp>`URL -> URL'</samp>
e68a7a

Complete server-side rename.

63f275

63f275
63f275
e68a7a

This command is an interface for Subversion's move command.

e68a7a
Options related to Subversion's move command can be passed
e68a7a
from third argument on. For example to specify a log message use the
e68a7a
<samp>`--message'</samp> option as follow:
e68a7a

e68a7a
centos-art path --move=URL/SRC --to=URL/DST --message 'Move url/src to url/dst'
e68a7a
e68a7a

For more information on Subversion's move functionality,

e68a7a
run the command: svn help move | less.
e68a7a

e68a7a
e68a7a
centos-art path --delete='SRC'
e68a7a

Use this command to remove files and directories from version control.

e68a7a
In this command, <tt>`SRC'</tt> can be a working copy (WC) path or URL. 
e68a7a

e68a7a
e68a7a
<samp>`WC'</samp>
e68a7a

Each item specified by a PATH is scheduled for deletion upon the next

e68a7a
commit.  Files, and directories that have not been committed, are
e68a7a
immediately removed from the working copy.  PATHs that are, or
e68a7a
contain, unversioned or modified items will not be removed unless the
e68a7a
<samp>`--force'</samp> option is given.
e68a7a

e68a7a
e68a7a
<samp>`URL'</samp>
e68a7a

Each item specified by a URL is deleted from the repository via an

e68a7a
immediate commit.
e68a7a

e68a7a
63f275
e68a7a

This command is an interface for Subversion's delete

e68a7a
command. Options related to Subversion's delete can be
e68a7a
passed from third argument on. For example to specify a log message
e68a7a
use the <samp>`--message'</samp> as follow:
e68a7a

e68a7a
centos-art path --delete='URL' --message 'Delete url.'
e68a7a
e68a7a

For more information on Subversion's delete functionality,

e68a7a
run the command: svn help delete | less.
e68a7a

e68a7a
e68a7a
centos-art path --sync='SRC'
e68a7a

Use this command to syncronize path information inside working copy.

e68a7a
This command is automatically used after moving or renaming parent
e68a7a
directories.  In this command, <tt>`SRC'</tt> is a working copy path
e68a7a
inside <tt>`trunk/Identity/'</tt> location, considered the parent
e68a7a
directory you want to syncronize path information for.
e68a7a

e68a7a
e68a7a
e68a7a
e68a7a
54264c

3.40.4 See also

4c79b5
e68a7a
e68a7a
3.36 trunk/Scripts/Bash  
e68a7a
e68a7a
3.37 trunk/Scripts/Bash/Functions  
e68a7a
e68a7a
4c79b5
4c79b5
4c79b5
e68a7a
[ < ]
e68a7a
[ > ]
4c79b5
   
4c79b5
[ << ]
cbf5a9
[ Up ]
e68a7a
[ >> ]
4c79b5
4c79b5

4c79b5
 <font size="-1">
008ee0
  This document was generated on December, 2 2010 using texi2html 1.76.
4c79b5
 </font>
4c79b5
 
4c79b5
4c79b5

4c79b5
</body>
4c79b5
</html>