r2848 - in trunk/BOOK: . basicnet/netprogs introduction/welcome server/other

randy at linuxfromscratch.org randy at linuxfromscratch.org
Tue Oct 19 17:03:14 PDT 2004


Author: randy
Date: 2004-10-19 18:03:12 -0600 (Tue, 19 Oct 2004)
New Revision: 2848

Modified:
   trunk/BOOK/basicnet/netprogs/subversion.xml
   trunk/BOOK/general.ent
   trunk/BOOK/introduction/welcome/changelog.xml
   trunk/BOOK/server/other/svnserver.xml
Log:
Updated to Subversion-1.1.0

Modified: trunk/BOOK/basicnet/netprogs/subversion.xml
===================================================================
--- trunk/BOOK/basicnet/netprogs/subversion.xml	2004-10-19 21:53:23 UTC (rev 2847)
+++ trunk/BOOK/basicnet/netprogs/subversion.xml	2004-10-20 00:03:12 UTC (rev 2848)
@@ -6,9 +6,10 @@
 
   <!ENTITY subversion-download-http "http://subversion.tigris.org/tarballs/subversion-&subversion-version;.tar.bz2">
   <!ENTITY subversion-download-ftp  " ">
-  <!ENTITY subversion-size          "5.8 MB">
-  <!ENTITY subversion-buildsize     "99 MB">
-  <!ENTITY subversion-time          "0.80 SBU">
+  <!ENTITY subversion-md5sum        "a91b0d79b8c8ab8747587037c044c6c9">
+  <!ENTITY subversion-size          "6.7 MB">
+  <!ENTITY subversion-buildsize     "650 MB">
+  <!ENTITY subversion-time          "1.39 SBU (additional 7.38 SBU to run tests)">
 ]>
 
 <sect1 id="subversion" xreflabel="Subversion-&subversion-version;">
@@ -22,45 +23,46 @@
 <sect2>
 <title>Introduction to <application>Subversion</application></title>
 
-<para><application>Subversion</application> is a version control system that 
-is designed to be a compelling replacement for <acronym>CVS</acronym>  in 
-the open source community.  It extends and enhances <acronym>CVS</acronym>'s 
-feature set, while maintaining a similar interface for those already familiar 
-with <acronym>CVS</acronym>.  These instructions install the client used to 
-manipulate a <application>Subversion</application> repository, creation of 
-a repository is covered at <xref linkend="svnserver"/>.</para>
+<para><application>Subversion</application> is a version control system 
+that is designed to be a compelling replacement for 
+<application><acronym>CVS</acronym></application> in the open source 
+community. It extends and enhances 
+<application><acronym>CVS</acronym></application>' feature set, while 
+maintaining a similar interface for those already familiar 
+with <application><acronym>CVS</acronym></application>. These instructions 
+install the client and server software used to manipulate a 
+<application>Subversion</application> repository. Creation of a repository is 
+covered at <xref linkend="svnserver"/>.</para>
 
 <sect3><title>Package information</title>
 <itemizedlist spacing='compact'>
 <listitem><para>Download (HTTP): <ulink url="&subversion-download-http;"/></para></listitem>
 <listitem><para>Download (FTP): <ulink url="&subversion-download-ftp;"/></para></listitem>
+<listitem><para>MD5 sum: &subversion-md5sum;</para></listitem>
 <listitem><para>Download size: &subversion-size;</para></listitem>
-<listitem><para>Estimated Disk space required: &subversion-buildsize;</para></listitem>
+<listitem><para>Estimated disk space required: &subversion-buildsize;</para></listitem>
 <listitem><para>Estimated build time: &subversion-time;</para></listitem></itemizedlist>
 </sect3>
 
 <sect3><title><application>Subversion</application> dependencies</title>
-<sect4><title>Required (client and server)</title>
-<para><xref linkend="libxml2"/></para></sect4>
-<sect4><title>Required (server only)</title>
-<para><xref linkend="db"/></para></sect4>
-<sect4><title>Optional (cleint and server)</title>
-<para>
-<xref linkend="expat"/>,
+<sect4><title>Required</title>
+<para><xref linkend="libxml2"/></para>
+</sect4>
+
+<sect4><title>Optional</title>
+<para><xref linkend="expat"/>, 
+<xref linkend="pkgconfig"/>, 
+<xref linkend="db"/>, 
 <xref linkend="gdbm"/>, 
-<xref linkend="openssl"/>,
-<xref linkend="openssh"/> and 
-<xref linkend="heimdal"/> or <xref linkend="mitkrb"/>
-</para></sect4>
-<sect4><title>Optional (server only)</title>
-<para>
-inetd or <xref linkend="xinetd" />,
-<xref linkend="apache"/>,
-<xref linkend="j2sdk"/>,
-<xref linkend="Python"/>,
-<ulink url="http://www.swig.org">SWIG</ulink> and
-<ulink url="http://www.webdav.org/neon/">neon-0.24.7</ulink>
-</para>
+<xref linkend="Python"/>, 
+<xref linkend="apache"/>, 
+<xref linkend="j2sdk"/>, 
+<xref linkend="openssl"/>, 
+<xref linkend="openssh"/>, 
+<xref linkend="heimdal"/> or <xref linkend="mitkrb"/>, 
+<ulink url="http://www.swig.org">SWIG</ulink>, 
+<ulink url="http://www.webdav.org/neon/">neon-0.24.7</ulink> and 
+inetd or <xref linkend="xinetd"/> (server only)</para>
 </sect4>
 </sect3>
 
@@ -69,18 +71,19 @@
 <sect2>
 <title>Installation of <application>Subversion</application></title>
 
-<para>Install <application>Subversion</application> by running the following commands:</para>
+<para>Install <application>Subversion</application> by running the following 
+commands:</para>
 
 <screen><userinput><command>./configure --prefix=/usr &&
 make &&
 make install</command></userinput></screen>
 
-<note><para>If you have <application>Apache</application> installed pass
+<note><para>If you have <application>Apache</application> installed, pass
 the <parameter>--with-apr=/usr</parameter> and
 <parameter>--with-apr-util=/usr</parameter> switches to the
 <command>configure</command> script. Otherwise,
 <application>Subversion</application> will overwrite
-<acronym>APR</acronym> and <acronym>APR</acronym>-utils from
+<acronym>APR</acronym> and <acronym>APR</acronym>-utils from the 
 <application>Apache</application> installation with its own
 files.</para></note>
 
@@ -90,7 +93,8 @@
 <title>Configuring <application>Subversion</application></title>
 
 <sect3><title>Config files</title>
-<para><filename>~/.subversion/config</filename>, <filename>/etc/subversion/config</filename></para>
+<para><filename>~/.subversion/config</filename> and 
+<filename>/etc/subversion/config</filename></para>
 </sect3>
 
 <sect3><title>Configuration Information</title>
@@ -101,7 +105,7 @@
 <command>svn</command> commands.</para>
 
 <para><filename>~/.subversion/config</filename> is the user's personal 
-configuration file.  It is used to override the system-wide defaults 
+configuration file. It is used to override the system-wide defaults 
 set in <filename>/etc/subversion/config</filename>.</para>
 </sect3>
 
@@ -111,10 +115,13 @@
 <title>Contents</title>
 
 <para>The <application>Subversion</application> package contains 
-<command>svn</command>, <command>svnversion</command>, 
-<command>svnlook</command>, <command>svnadmin</command>,
-<command>svndumpfilter</command>, <command>mod_dav_svn</command> 
-and <command>svnserve</command>.</para>
+<command>svn</command>, 
+<command>svnadmin</command>, 
+<command>svndumpfilter</command>, 
+<command>svnlook</command>, 
+<command>svnserve</command>, 
+<command>svnversion</command> and the 
+<filename class="libraryfile">mod_dav_svn</filename> plug-in module.</para>
 
 </sect2>
 
@@ -123,28 +130,30 @@
 <sect3><title>svn</title>
 <para>The command-line client program.</para></sect3>
 
-<sect3><title>svnversion</title>
-<para>A program for reporting the state of a working copy.</para></sect3>
+<sect3><title>svnadmin</title>
+<para>A tool for creating, tweaking or repairing a 
+<application>Subversion</application> repository.</para></sect3>
 
+<sect3><title>svndumpfilter</title>
+<para>A program for filtering <application>Subversion</application> repository 
+dumpfile format streams.</para></sect3>
+
 <sect3><title>svnlook</title>
-<para>A tool for inspecting a Subversion repository.</para></sect3>
-
-<sect3><title>svnadmin</title>
-<para>A tool for creating, tweaking or repairing a Subversion 
+<para>A tool for inspecting a <application>Subversion</application> 
 repository.</para></sect3>
 
-<sect3><title>svndumpfilter</title>
-<para>A program for filtering Subversion repository dumpfile format 
-streams.</para></sect3>
+<sect3><title>svnserve</title>
+<para>A custom standalone server program, able to run as a daemon process or 
+invoked by <acronym>SSH</acronym>.</para></sect3>
 
+<sect3><title>svnversion</title>
+<para>A program for reporting the state of a working copy.</para></sect3>
+
 <sect3><title>mod_dav_svn</title>
-<para>A plug-in module for the Apache HTTP Server, used to make your 
+<para>A plug-in module for the <application>Apache</application> 
+<acronym>HTTP</acronym> Server, used to make your 
 repository available to others over a network.</para></sect3>
 
-<sect3><title>svnserve</title>
-<para>A custom standalone server program, able to run as a daemon process or 
-invoked  by <acronym>SSH</acronym>.</para></sect3>
-
 </sect2>
 
 </sect1>

Modified: trunk/BOOK/general.ent
===================================================================
--- trunk/BOOK/general.ent	2004-10-19 21:53:23 UTC (rev 2847)
+++ trunk/BOOK/general.ent	2004-10-20 00:03:12 UTC (rev 2848)
@@ -168,7 +168,7 @@
 <!ENTITY openssh-version              "3.9p1"> 
 <!ENTITY rsync-version                "2.6.2"> 
 <!ENTITY cvs-version                  "1.11.17">  
-<!ENTITY subversion-version           "1.0.6">
+<!ENTITY subversion-version           "1.1.0">
 <!ENTITY wget-version                 "1.9.1">  
 <!ENTITY tcpwrappers-version          "7.6">  
 <!ENTITY portmap-version              "5beta">    

Modified: trunk/BOOK/introduction/welcome/changelog.xml
===================================================================
--- trunk/BOOK/introduction/welcome/changelog.xml	2004-10-19 21:53:23 UTC (rev 2847)
+++ trunk/BOOK/introduction/welcome/changelog.xml	2004-10-20 00:03:12 UTC (rev 2848)
@@ -26,7 +26,8 @@
 PHP-5.0.2.</para></listitem>
 
 <listitem><para>October 19th, 2004 [randy]: Rearranged build order in 
-Thunderbird instructions to correct a minor build problem.</para></listitem>
+Thunderbird instructions to correct a minor build problem; updated to
+Subversion-1.1.0.</para></listitem>
 
 <listitem><para>October 19th, 2004 [larry]: Updated to
 xfs-2.6.25, reiserfs-3.6.19, nano-1.2.3 and krb5-1.3.5.</para></listitem>

Modified: trunk/BOOK/server/other/svnserver.xml
===================================================================
--- trunk/BOOK/server/other/svnserver.xml	2004-10-19 21:53:23 UTC (rev 2847)
+++ trunk/BOOK/server/other/svnserver.xml	2004-10-20 00:03:12 UTC (rev 2848)
@@ -21,7 +21,8 @@
 
 <sect3><title><application>Subversion server</application> dependencies</title>
 <sect4><title>Required</title>
-<para><xref linkend="subversion"/> and <xref linkend="openssh"/></para></sect4>
+<para><xref linkend="subversion"/> and <xref linkend="openssh"/></para>
+</sect4>
 </sect3>
 
 </sect2>
@@ -37,25 +38,25 @@
 <para>Configuration of the <application>Subversion</application> server 
 consists of the following steps:</para>
                                                                                 
-<sect3><title>1.  Setup users, groups, and permissions</title>
+<sect3><title>1. Setup users, groups, and permissions</title>
 <para>You'll need to be user root for the initial portion of
-configuration.  Create the svn user and group with the following 
+configuration. Create the svn user and group with the following 
 commands:</para>
 
 <screen><userinput><command>groupadd svn &&
 useradd -c "SVN Owner" -d /home/svn -m -g svn -s /bin/false svn</command></userinput></screen>
 
 <para>If you plan to have multiple repositories, you should have a 
-group dedicated to each repository for ease of administration.  Create
-the svntest group for our test repository and add the svn user to that
+group dedicated to each repository for ease of administration. Create 
+the svntest group for the test repository and add the svn user to that
 group with the following commands:</para>
 
 <screen><userinput><command>groupadd svntest &&
 usermod -G svntest svn</command></userinput></screen>
 
-<para>Additionally you should set umask '002' while working with a
-repository so that all new files will be writable by owner and group.
-We'll make this mandatory by writing a wrapper script for
+<para>Additionally you should set <command>umask 002</command> while working 
+with a repository so that all new files will be writable by owner and group.
+This is made mandatory by creating a wrapper script for
 <command>svn</command> and <command>svnserve</command>:</para>
 
 <screen><userinput><command>mv /usr/bin/svn /usr/bin/svn.orig &&
@@ -72,23 +73,25 @@
 <command>EOF
 chmod 0755 /usr/bin/svn{,serve}</command></userinput></screen>
 
-<note><para>If you use <application>apache</application> for working with 
-the repository over http, even for anonymous access, you should wrap 
-<application>apache</application> in a similar script.</para></note>
+<note><para>If you use <application>Apache</application> for working with 
+the repository over <acronym>HTTP</acronym>, even for anonymous access, you 
+should wrap <command>/usr/sbin/httpd</command> in a similar 
+script.</para></note>
 
 </sect3>
 
-<sect3><title>2.  Create a <application>Subversion</application>
+<sect3><title>2. Create a <application>Subversion</application>
 repository.</title>
 <para>Create a new <application>Subversion</application> repository with
 the following commands:</para>
+
 <screen><userinput><command>install -d -m0755 /srv &&
 install -d -m0755 -o svn -g svn /srv/svn/repositories &&
 svnadmin create /srv/svn/repositories/svntest</command></userinput></screen>
 
 <para>Now that the repository is created, we need to populate it with
-something useful.  You'll need to have a predefined directory layout 
-setup exactly as you want your repository to look.  For example, here 
+something useful. You'll need to have a predefined directory layout 
+setup exactly as you want your repository to look. For example, here 
 is a sample BLFS layout setup with a root of <filename>svntest/</filename>.
 You'll need to setup a directory tree similar to the following:</para>
 
@@ -102,8 +105,8 @@
              branches/        # Needed for additional branches
              tags/            # Needed for tagging release points</screen>
 
-<para>Once you've created your directory layout as above, you are ready to 
-do the initial import:</para>
+<para>Once you've created your directory layout as shown above, you are ready 
+to do the initial import:</para>
 
 <screen><userinput><command>svn import -m "Initial import." \
     <replaceable>[/path/to/source/tree]</replaceable> \
@@ -117,41 +120,42 @@
 chmod g+s /srv/svn/repositories/svntest/db &&
 usermod -G svn,svntest,<replaceable>[insert existing groups]</replaceable> <replaceable>[username]</replaceable></command></userinput></screen>
 
-<para>svntest is the group assigned to the svntest repository.  As
+<para>svntest is the group assigned to the svntest repository. As
 mentioned earlier, this eases administration of multiple repositories
-when using <application>OpenSSH</application> for authentication.  Going 
+when using <application>OpenSSH</application> for authentication. Going 
 forward, you'll need to add your regular user, and any additional users 
 that you wish to have write access to the repository, to the svn and 
 svntest groups.</para>
          
 <para>In addition, you'll notice that the new repository's
-<filename>db</filename> directory is set-groupID.  If the reasoning is 
+<filename>db</filename> directory is set-groupID. If the reasoning is 
 not immediately obvious, when using any external authentication method 
-(such as ssh), the sticky bit is set so that all new files will be owned
-by the user, but group of svntest.  Anyone in the svntest group can 
-create files, but still give the entire group write access to those 
-files.  This avoids locking out other users from the repository.</para>
+(such as <command>ssh</command>), the sticky bit is set so that all new files 
+will be owned by the user, but group of svntest. Anyone in the svntest group 
+can create files, but still give the entire group write access to those 
+files. This avoids locking out other users from the repository.</para>
 
 <para>Now, go ahead and return to your normal user account, and take a look at 
 your new repository using <command>svnlook</command>:</para>
 
 <screen><userinput><command>svnlook tree /srv/svn/repositories/svntest/</command></userinput></screen>
 
-<note><para>You may need to logout and back in again to refresh your group
-memberships.  '<command>su <replaceable>[username]</replaceable></command>' 
+<note><para>You may need to log out and back in again to refresh your group
+memberships. '<command>su <replaceable>[username]</replaceable></command>' 
 should work around this as well.</para></note>
 
 </sect3>
 
-<sect3><title>3.  Configure the server</title>
+<sect3><title>3. Configure the server</title>
 
 <para>As mentioned previously, these instructions will configure the 
-server to use only ssh for write access to the repository and to provide 
-anonymous access using <command>svnserve</command>.  There are several other 
-ways to provide access to the repository.  These additional configurations 
-are best explained at <ulink url="http://svnbook.red-bean.com/" />.</para>
+server to use only <command>ssh</command> for write access to the repository 
+and to provide anonymous access using <command>svnserve</command>. There are 
+several other ways to provide access to the repository. These additional 
+configurations are best explained at 
+<ulink url="http://svnbook.red-bean.com/"/>.</para>
 
-<para>Access configuration needs to be done for each repository.  Create 
+<para>Access configuration needs to be done for each repository. Create 
 the <filename>svnserve.conf</filename> file for the svntest repository 
 using the following commands:</para>
 
@@ -163,17 +167,17 @@
 auth-access = write
 <command>EOF</command></userinput></screen>
 
-<para>There is not a lot to the configuration file at all.  You'll notice 
-that only the general section is required.  Take a look at the
-<filename>svnserve.conf.default</filename> for information on using
+<para>There is not a lot to the configuration file at all. You'll notice 
+that only the general section is required. Take a look at the
+<filename>svnserve.conf.default</filename> file for information on using 
 <command>svnserve</command>'s built-in authentication method.</para>
 
 </sect3>
 
-<sect3><title>4.  Starting the server</title>
-<para>There are a couple of ways to start <command>svnserve</command>.  The
-most common way is to start it as an <application>inetd</application> or 
-<application>xinetd</application> process.  Alternately, you can use a
+<sect3><title>4. Starting the server</title>
+<para>There are a couple of ways to start <command>svnserve</command>. The 
+most common way is to start it as an <command>inetd</command> or 
+<command>xinetd</command> process. Alternately, you can use a 
 bootscript to start the service at startup.</para>
 
 <note><para>If you do not wish to provide anonymous access to your svn
@@ -181,15 +185,15 @@
 authentication, you do not need to run 
 <command>svnserve</command>.</para></note>
 
-<para>If you use <application>inetd</application>, add a line to your
+<para>If you use <command>inetd</command>, add a line to 
 <filename>/etc/inetd.conf</filename> using the following commands:</para>
 
 <screen><userinput><command>cat >> /etc/inetd.conf << "EOF"</command>
 svn stream tcp nowait svn /usr/bin/svnserve svnserve -i
 <command>EOF</command></userinput></screen>
 
-<para>If you use <application>xinetd</application>, add the following
-lines to <filename>/etc/xinetd.conf</filename> file:</para>
+<para>If you use <command>xinetd</command>, add the following
+lines to the <filename>/etc/xinetd.conf</filename> file:</para>
 
 <screen><userinput><command>cat >> /etc/xinetd.conf << "EOF"</command>
 service svn




More information about the blfs-book mailing list