esvn.xml

linux 下的 图形化的 SVN 相当于 VSS

                                <action>Logoff</action> root <command>exit</command>.</para>
                        </step>
                        <step>
                            <para>
                                <action>Type</action>
                                <command>&esvn;</command> to start &esvn;.</para>
                        </step>
                    </procedure>
                    <tip>
                        <para>If you are running <application class="software">KDE</application> or
                            have <application>KPackage</application> installed, <action>run</action>
                            <application>KPackage</application> then <action>drag-drop</action> the
                            <acronym>RPM</acronym> onto <application>KPackage</application>. This
                            method is recommended for new users who are not sure about how to check
                            dependencies etc.</para>
                    </tip>
                </sect3>
            </sect2>
            <sect2 id="esvn-upgrading">
                <title>Upgrading</title>
                <para>From time-to-time new versions of &esvn; are released with new features,
                    functionality and fixes to bugs. When this happens you will want to upgrade. If
                    you installed &esvn; from a RPM see <xref linkend="esvn-rpm-upgrade"
                    endterm="esvn-title-rpm-upgrade"/>. If you installed from a tarball see <xref
                        linkend="esvn-title-tar-upgrade" endterm="esvn-title-tar-upgrade"/>.</para>
                <tip>
                    <para>Select &help-checkupdates; to check the &esvn; web site for new
                        versions (see <xref linkend="esvn-checking-versions"/>).</para>
                </tip>
                <sect3 id="esvn-rpm-upgrade">
                    <title id="esvn-title-rpm-upgrade">RPM Upgrade</title>
                    <para>To upgrade a RPM installation of &esvn; follow the procedure below.</para>
                    <procedure>
                        <title>RPM Upgrade</title>
                        <step>
                            <para>Download the latest RPM package.</para>
                        </step>
                        <step>
                            <para>Start a <application>Shell</application> session.</para>
                        </step>
                        <step>
                            <para>Change to the folder where the RPM package is located (<command>cd path/to/package/</command>).</para>
                        </step>
                        <step>
                            <para>Login as root (<command>su</command> and <command>
                                    <replaceable>password</replaceable>
                                </command>).</para>
                        </step>
                        <step>
                            <para>Enter the following command <command>rpm -Uvh [package]</command>.
                                This will upgrade the existing installation and show progress of the operation.</para>
                        </step>
                        <step>
                            <para>Logoff Super User session (<command>exit</command>).</para>
                            <para>To start &esvn; see <xref linkend="esvn-starting"/>.</para>
                        </step>
                    </procedure>
                </sect3>
                <sect3 id="esvn-tar-upgrade">
                    <title id="esvn-title-tar-upgrade">Tarball Upgrade</title>
                    <!-- Not sure on the procedure how to do this  Just as a regular install, make && make install -->
                    <para>TBD</para>
                </sect3>
            </sect2>
            <sect2 id="esvn-inst-uninst">
                <title>Uninstalling</title>
                <para>You may wish to uninstall &esvn;. The method used depends on how you
                    performed the installation. If you installed using tarball see <xref
                    linkend="esvn-uninst-tarball"/>. If you used <acronym>RPM</acronym> see <xref linkend="esvn-uninst-rpm"/>.</para>
                <sect3 id="esvn-uninst-tarball">
                    <title>uninstall tarball installation</title>
                    <para>To uninstall &esvn; when the installation was performed from a
                        tarball, proceed as follows:</para>
                    <procedure>
                        <title>Uninstall tarball installation</title>
                        <step>
                            <para>
                                <action>Open</action> a <application>Shell</application> session.</para>
                        </step>
                        <step>
                            <para>
                                <action>login</action> as root <command>su</command>, then enter the
                                root password.</para>
                        </step>
                        <step>
                            <para>Change to the directory where you did <command>make</command> in
                                the tarball (<command>cd path/to/installation/make/folder</command>).</para>
                        </step>
                        <step>
                            <para>
                                <action>Type</action>
                                <command>make uninstall</command>.</para>
                        </step>
                    </procedure>
                    <note>
                        <para>The folder containing the extracted archive can be removed if no
                            longer required.</para>
                    </note>
                </sect3>
                <sect3 id="esvn-uninst-rpm">
                    <title>Uninstall RPM installation</title>
                    <para>To uninstall &esvn; when the installation was performed from a RPM,
                        proceed as follows:</para>
                    <procedure>
                        <title>Uninstall RPM installation</title>
                        <step>
                            <para>
                                <action>Open</action> a <application>Shell</application> session.</para>
                        </step>
                        <step>
                            <para>
                                <action>login</action> as root <command>su</command>, then enter the
                                root password.</para>
                        </step>
                        <step>
                            <para>
                                <action>Type</action>
                                <command>rpm -e esvn</command>.</para>
                        </step>
                        <step>
                            <para>
                                <action>Logoff</action> root <command>exit</command>.</para>
                        </step>
                    </procedure>
                </sect3>
            </sect2>
        </sect1>
        <sect1 id="esvn-checking-versions">
            <title>Checking for new versions</title>
            <para>From time-to-time new versions of &esvn; are released in order to introduce
                new features and functions. There are tow types of version releases:</para>
            <itemizedlist spacing="compact">
                <listitem>
                    <para>
                        <emphasis role="bold">Stable</emphasis> - these versions include features
                        that have been tested and are generally considered safe.</para>
                </listitem>
                <listitem>
                    <para>
                        <emphasis role="bold">Testing</emphasis> - these version are fresh from the
                        oven, they include the latest additions and are not guaranteed to work
                        without a bump or two.</para>
                </listitem>
            </itemizedlist>
            <para>With &esvn; it is easy to discover which version you have installed and what
                the latest stable and testing releases are by selecting &help-checkupdates;.
                This displays the <interfacename>Version update</interfacename> dialog with the
                following options:</para>
            <figure id="fig-update-version" condition="fo">
                <title>Version update</title>
                <screenshot>
                    <mediaobject>
                        <imageobject>
                            <imagedata fileref="images/version-update.png" format="PNG" width="5cm"/>
                        </imageobject>
                    </mediaobject>
                </screenshot>
            </figure>
            <variablelist>
                <varlistentry>
                    <term>Current version</term>
                    <listitem>
                        <para>The version number installed.</para>
                    </listitem>
                </varlistentry>
                <varlistentry>
                    <term>Latest stable version</term>
                    <listitem>
                        <para>The last stable release. <action>Click</action>
                            <guibutton>Update</guibutton> to display information about the stable
                            release in the default <application>Web browser</application>.</para>
                    </listitem>
                </varlistentry>
                <varlistentry>
                    <term>Latest testing version</term>
                    <listitem>
                        <para>The last testing release. <action>Click</action>
                            <guibutton>Update</guibutton> to display information about the testing
                            release in the default <application>Web browser</application>.</para>
                    </listitem>
                </varlistentry>
                <varlistentry>
                    <term>All versions</term>
                    <listitem>
                        <para>
                            <action>Click</action>
                            <guibutton>All versions</guibutton> to display information about all
                            releases in the default <application>Web browser</application>.</para>
                    </listitem>
                </varlistentry>
            </variablelist>
        </sect1>
    </preface>
    <chapter id="esvn-overview">
        <title>Overview</title>
        <para>
            <application>&esvn;</application> is a <acronym>GUI</acronym> front end to <application>
                <ulink url="http://subversion.tigris.org/">subversion</ulink>
            </application> (<acronym>SVN</acronym>), a version control system developed by the
                <ulink url="http://www.tigris.org">Tigris</ulink> community of Open Source
            developers. For those who are familiar with <application>
                <ulink url="https://www.cvshome.org/">Concurrent Versions System</ulink>
            </application> (<acronym>CVS</acronym>), <application>subversion</application> is
            <acronym>CVS</acronym> without the wrinkles, complexity and inefficiency of
            <acronym>CVS</acronym>. Since <application>&esvn;</application> is a front end
            application it relies on having <application>subversion</application> installed.</para>
        <para>The main purpose of <application>subversion</application> is to be a file server that
            provides revision control services for a given tree of folders and the files they
            contain. Users can work in two ways with the file system, they can:</para>
        <itemizedlist>
            <listitem>
                <para>access files directly over the network, or</para>
            </listitem>
            <listitem>
                <para>checkout a copy of the files to their local machine</para>
            </listitem>
        </itemizedlist>
        <para>Both methods enable users with the right permissions to perform common operations such
            as create, modify, delete, copy, move. The difference between a normal file server and a
            <application>subversion</application> server is that a
            <application>subversion</application> server tracks and logs all changes to the
            repository and keeps copies thereof. The advantage of this is that multiple users can
            have simultaneous access to the file system. Each user can make changes and commit them