Changeset 01d5424


Ignore:
Timestamp:
10/20/2004 12:03:12 AM (20 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 12.2, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gimp3, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/for-12.3, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/spidermonkey128, xry111/test-20220226, xry111/xf86-video-removal
Children:
e16d90ee
Parents:
84e42bc
Message:

Updated to Subversion-1.1.0

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@2848 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:
4 edited

Legend:

Unmodified
Added
Removed
  • basicnet/netprogs/subversion.xml

    r84e42bc r01d5424  
    77  <!ENTITY subversion-download-http "http://subversion.tigris.org/tarballs/subversion-&subversion-version;.tar.bz2">
    88  <!ENTITY subversion-download-ftp  " ">
    9   <!ENTITY subversion-size          "5.8 MB">
    10   <!ENTITY subversion-buildsize     "99 MB">
    11   <!ENTITY subversion-time          "0.80 SBU">
     9  <!ENTITY subversion-md5sum        "a91b0d79b8c8ab8747587037c044c6c9">
     10  <!ENTITY subversion-size          "6.7 MB">
     11  <!ENTITY subversion-buildsize     "650 MB">
     12  <!ENTITY subversion-time          "1.39 SBU (additional 7.38 SBU to run tests)">
    1213]>
    1314
     
    2324<title>Introduction to <application>Subversion</application></title>
    2425
    25 <para><application>Subversion</application> is a version control system that
    26 is designed to be a compelling replacement for <acronym>CVS</acronym>  in
    27 the open source community.  It extends and enhances <acronym>CVS</acronym>'s
    28 feature set, while maintaining a similar interface for those already familiar
    29 with <acronym>CVS</acronym>.  These instructions install the client used to
    30 manipulate a <application>Subversion</application> repository, creation of
    31 a repository is covered at <xref linkend="svnserver"/>.</para>
     26<para><application>Subversion</application> is a version control system
     27that is designed to be a compelling replacement for
     28<application><acronym>CVS</acronym></application> in the open source
     29community. It extends and enhances
     30<application><acronym>CVS</acronym></application>' feature set, while
     31maintaining a similar interface for those already familiar
     32with <application><acronym>CVS</acronym></application>. These instructions
     33install the client and server software used to manipulate a
     34<application>Subversion</application> repository. Creation of a repository is
     35covered at <xref linkend="svnserver"/>.</para>
    3236
    3337<sect3><title>Package information</title>
     
    3539<listitem><para>Download (HTTP): <ulink url="&subversion-download-http;"/></para></listitem>
    3640<listitem><para>Download (FTP): <ulink url="&subversion-download-ftp;"/></para></listitem>
     41<listitem><para>MD5 sum: &subversion-md5sum;</para></listitem>
    3742<listitem><para>Download size: &subversion-size;</para></listitem>
    38 <listitem><para>Estimated Disk space required: &subversion-buildsize;</para></listitem>
     43<listitem><para>Estimated disk space required: &subversion-buildsize;</para></listitem>
    3944<listitem><para>Estimated build time: &subversion-time;</para></listitem></itemizedlist>
    4045</sect3>
    4146
    4247<sect3><title><application>Subversion</application> dependencies</title>
    43 <sect4><title>Required (client and server)</title>
    44 <para><xref linkend="libxml2"/></para></sect4>
    45 <sect4><title>Required (server only)</title>
    46 <para><xref linkend="db"/></para></sect4>
    47 <sect4><title>Optional (cleint and server)</title>
    48 <para>
    49 <xref linkend="expat"/>,
     48<sect4><title>Required</title>
     49<para><xref linkend="libxml2"/></para>
     50</sect4>
     51
     52<sect4><title>Optional</title>
     53<para><xref linkend="expat"/>,
     54<xref linkend="pkgconfig"/>,
     55<xref linkend="db"/>,
    5056<xref linkend="gdbm"/>,
    51 <xref linkend="openssl"/>,
    52 <xref linkend="openssh"/> and
    53 <xref linkend="heimdal"/> or <xref linkend="mitkrb"/>
    54 </para></sect4>
    55 <sect4><title>Optional (server only)</title>
    56 <para>
    57 inetd or <xref linkend="xinetd" />,
    58 <xref linkend="apache"/>,
    59 <xref linkend="j2sdk"/>,
    60 <xref linkend="Python"/>,
    61 <ulink url="http://www.swig.org">SWIG</ulink> and
    62 <ulink url="http://www.webdav.org/neon/">neon-0.24.7</ulink>
    63 </para>
     57<xref linkend="Python"/>,
     58<xref linkend="apache"/>,
     59<xref linkend="j2sdk"/>,
     60<xref linkend="openssl"/>,
     61<xref linkend="openssh"/>,
     62<xref linkend="heimdal"/> or <xref linkend="mitkrb"/>,
     63<ulink url="http://www.swig.org">SWIG</ulink>,
     64<ulink url="http://www.webdav.org/neon/">neon-0.24.7</ulink> and
     65inetd or <xref linkend="xinetd"/> (server only)</para>
    6466</sect4>
    6567</sect3>
     
    7072<title>Installation of <application>Subversion</application></title>
    7173
    72 <para>Install <application>Subversion</application> by running the following commands:</para>
     74<para>Install <application>Subversion</application> by running the following
     75commands:</para>
    7376
    7477<screen><userinput><command>./configure --prefix=/usr &amp;&amp;
     
    7679make install</command></userinput></screen>
    7780
    78 <note><para>If you have <application>Apache</application> installed pass
     81<note><para>If you have <application>Apache</application> installed, pass
    7982the <parameter>--with-apr=/usr</parameter> and
    8083<parameter>--with-apr-util=/usr</parameter> switches to the
    8184<command>configure</command> script. Otherwise,
    8285<application>Subversion</application> will overwrite
    83 <acronym>APR</acronym> and <acronym>APR</acronym>-utils from
     86<acronym>APR</acronym> and <acronym>APR</acronym>-utils from the
    8487<application>Apache</application> installation with its own
    8588files.</para></note>
     
    9194
    9295<sect3><title>Config files</title>
    93 <para><filename>~/.subversion/config</filename>, <filename>/etc/subversion/config</filename></para>
     96<para><filename>~/.subversion/config</filename> and
     97<filename>/etc/subversion/config</filename></para>
    9498</sect3>
    9599
     
    102106
    103107<para><filename>~/.subversion/config</filename> is the user's personal
    104 configuration file.  It is used to override the system-wide defaults
     108configuration file. It is used to override the system-wide defaults
    105109set in <filename>/etc/subversion/config</filename>.</para>
    106110</sect3>
     
    112116
    113117<para>The <application>Subversion</application> package contains
    114 <command>svn</command>, <command>svnversion</command>,
    115 <command>svnlook</command>, <command>svnadmin</command>,
    116 <command>svndumpfilter</command>, <command>mod_dav_svn</command>
    117 and <command>svnserve</command>.</para>
     118<command>svn</command>,
     119<command>svnadmin</command>,
     120<command>svndumpfilter</command>,
     121<command>svnlook</command>,
     122<command>svnserve</command>,
     123<command>svnversion</command> and the
     124<filename class="libraryfile">mod_dav_svn</filename> plug-in module.</para>
    118125
    119126</sect2>
     
    124131<para>The command-line client program.</para></sect3>
    125132
     133<sect3><title>svnadmin</title>
     134<para>A tool for creating, tweaking or repairing a
     135<application>Subversion</application> repository.</para></sect3>
     136
     137<sect3><title>svndumpfilter</title>
     138<para>A program for filtering <application>Subversion</application> repository
     139dumpfile format streams.</para></sect3>
     140
     141<sect3><title>svnlook</title>
     142<para>A tool for inspecting a <application>Subversion</application>
     143repository.</para></sect3>
     144
     145<sect3><title>svnserve</title>
     146<para>A custom standalone server program, able to run as a daemon process or
     147invoked by <acronym>SSH</acronym>.</para></sect3>
     148
    126149<sect3><title>svnversion</title>
    127150<para>A program for reporting the state of a working copy.</para></sect3>
    128151
    129 <sect3><title>svnlook</title>
    130 <para>A tool for inspecting a Subversion repository.</para></sect3>
    131 
    132 <sect3><title>svnadmin</title>
    133 <para>A tool for creating, tweaking or repairing a Subversion
    134 repository.</para></sect3>
    135 
    136 <sect3><title>svndumpfilter</title>
    137 <para>A program for filtering Subversion repository dumpfile format
    138 streams.</para></sect3>
    139 
    140152<sect3><title>mod_dav_svn</title>
    141 <para>A plug-in module for the Apache HTTP Server, used to make your
     153<para>A plug-in module for the <application>Apache</application>
     154<acronym>HTTP</acronym> Server, used to make your
    142155repository available to others over a network.</para></sect3>
    143 
    144 <sect3><title>svnserve</title>
    145 <para>A custom standalone server program, able to run as a daemon process or
    146 invoked  by <acronym>SSH</acronym>.</para></sect3>
    147156
    148157</sect2>
  • general.ent

    r84e42bc r01d5424  
    169169<!ENTITY rsync-version                "2.6.2">
    170170<!ENTITY cvs-version                  "1.11.17"> 
    171 <!ENTITY subversion-version           "1.0.6">
     171<!ENTITY subversion-version           "1.1.0">
    172172<!ENTITY wget-version                 "1.9.1"> 
    173173<!ENTITY tcpwrappers-version          "7.6"> 
  • introduction/welcome/changelog.xml

    r84e42bc r01d5424  
    2727
    2828<listitem><para>October 19th, 2004 [randy]: Rearranged build order in
    29 Thunderbird instructions to correct a minor build problem.</para></listitem>
     29Thunderbird instructions to correct a minor build problem; updated to
     30Subversion-1.1.0.</para></listitem>
    3031
    3132<listitem><para>October 19th, 2004 [larry]: Updated to
  • server/other/svnserver.xml

    r84e42bc r01d5424  
    2222<sect3><title><application>Subversion server</application> dependencies</title>
    2323<sect4><title>Required</title>
    24 <para><xref linkend="subversion"/> and <xref linkend="openssh"/></para></sect4>
     24<para><xref linkend="subversion"/> and <xref linkend="openssh"/></para>
     25</sect4>
    2526</sect3>
    2627
     
    3839consists of the following steps:</para>
    3940                                                                               
    40 <sect3><title>1.  Setup users, groups, and permissions</title>
     41<sect3><title>1. Setup users, groups, and permissions</title>
    4142<para>You'll need to be user root for the initial portion of
    42 configuration.  Create the svn user and group with the following
     43configuration. Create the svn user and group with the following
    4344commands:</para>
    4445
     
    4748
    4849<para>If you plan to have multiple repositories, you should have a
    49 group dedicated to each repository for ease of administration.  Create
    50 the svntest group for our test repository and add the svn user to that
     50group dedicated to each repository for ease of administration. Create
     51the svntest group for the test repository and add the svn user to that
    5152group with the following commands:</para>
    5253
     
    5455usermod -G svntest svn</command></userinput></screen>
    5556
    56 <para>Additionally you should set umask '002' while working with a
    57 repository so that all new files will be writable by owner and group.
    58 We'll make this mandatory by writing a wrapper script for
     57<para>Additionally you should set <command>umask 002</command> while working
     58with a repository so that all new files will be writable by owner and group.
     59This is made mandatory by creating a wrapper script for
    5960<command>svn</command> and <command>svnserve</command>:</para>
    6061
     
    7374chmod 0755 /usr/bin/svn{,serve}</command></userinput></screen>
    7475
    75 <note><para>If you use <application>apache</application> for working with
    76 the repository over http, even for anonymous access, you should wrap
    77 <application>apache</application> in a similar script.</para></note>
    78 
    79 </sect3>
    80 
    81 <sect3><title>2.  Create a <application>Subversion</application>
     76<note><para>If you use <application>Apache</application> for working with
     77the repository over <acronym>HTTP</acronym>, even for anonymous access, you
     78should wrap <command>/usr/sbin/httpd</command> in a similar
     79script.</para></note>
     80
     81</sect3>
     82
     83<sect3><title>2. Create a <application>Subversion</application>
    8284repository.</title>
    8385<para>Create a new <application>Subversion</application> repository with
    8486the following commands:</para>
     87
    8588<screen><userinput><command>install -d -m0755 /srv &amp;&amp;
    8689install -d -m0755 -o svn -g svn /srv/svn/repositories &amp;&amp;
     
    8891
    8992<para>Now that the repository is created, we need to populate it with
    90 something useful.  You'll need to have a predefined directory layout
    91 setup exactly as you want your repository to look.  For example, here
     93something useful. You'll need to have a predefined directory layout
     94setup exactly as you want your repository to look. For example, here
    9295is a sample BLFS layout setup with a root of <filename>svntest/</filename>.
    9396You'll need to setup a directory tree similar to the following:</para>
     
    103106             tags/            # Needed for tagging release points</screen>
    104107
    105 <para>Once you've created your directory layout as above, you are ready to
    106 do the initial import:</para>
     108<para>Once you've created your directory layout as shown above, you are ready
     109to do the initial import:</para>
    107110
    108111<screen><userinput><command>svn import -m "Initial import." \
     
    118121usermod -G svn,svntest,<replaceable>[insert existing groups]</replaceable> <replaceable>[username]</replaceable></command></userinput></screen>
    119122
    120 <para>svntest is the group assigned to the svntest repository.  As
     123<para>svntest is the group assigned to the svntest repository. As
    121124mentioned earlier, this eases administration of multiple repositories
    122 when using <application>OpenSSH</application> for authentication.  Going
     125when using <application>OpenSSH</application> for authentication. Going
    123126forward, you'll need to add your regular user, and any additional users
    124127that you wish to have write access to the repository, to the svn and
     
    126129         
    127130<para>In addition, you'll notice that the new repository's
    128 <filename>db</filename> directory is set-groupID.  If the reasoning is
     131<filename>db</filename> directory is set-groupID. If the reasoning is
    129132not immediately obvious, when using any external authentication method
    130 (such as ssh), the sticky bit is set so that all new files will be owned
    131 by the user, but group of svntest.  Anyone in the svntest group can
    132 create files, but still give the entire group write access to those
    133 files.  This avoids locking out other users from the repository.</para>
     133(such as <command>ssh</command>), the sticky bit is set so that all new files
     134will be owned by the user, but group of svntest. Anyone in the svntest group
     135can create files, but still give the entire group write access to those
     136files. This avoids locking out other users from the repository.</para>
    134137
    135138<para>Now, go ahead and return to your normal user account, and take a look at
     
    138141<screen><userinput><command>svnlook tree /srv/svn/repositories/svntest/</command></userinput></screen>
    139142
    140 <note><para>You may need to logout and back in again to refresh your group
    141 memberships.  '<command>su <replaceable>[username]</replaceable></command>'
     143<note><para>You may need to log out and back in again to refresh your group
     144memberships. '<command>su <replaceable>[username]</replaceable></command>'
    142145should work around this as well.</para></note>
    143146
    144147</sect3>
    145148
    146 <sect3><title>3.  Configure the server</title>
     149<sect3><title>3. Configure the server</title>
    147150
    148151<para>As mentioned previously, these instructions will configure the
    149 server to use only ssh for write access to the repository and to provide
    150 anonymous access using <command>svnserve</command>.  There are several other
    151 ways to provide access to the repository.  These additional configurations
    152 are best explained at <ulink url="http://svnbook.red-bean.com/" />.</para>
    153 
    154 <para>Access configuration needs to be done for each repository.  Create
     152server to use only <command>ssh</command> for write access to the repository
     153and to provide anonymous access using <command>svnserve</command>. There are
     154several other ways to provide access to the repository. These additional
     155configurations are best explained at
     156<ulink url="http://svnbook.red-bean.com/"/>.</para>
     157
     158<para>Access configuration needs to be done for each repository. Create
    155159the <filename>svnserve.conf</filename> file for the svntest repository
    156160using the following commands:</para>
     
    164168<command>EOF</command></userinput></screen>
    165169
    166 <para>There is not a lot to the configuration file at all.  You'll notice
    167 that only the general section is required.  Take a look at the
    168 <filename>svnserve.conf.default</filename> for information on using
     170<para>There is not a lot to the configuration file at all. You'll notice
     171that only the general section is required. Take a look at the
     172<filename>svnserve.conf.default</filename> file for information on using
    169173<command>svnserve</command>'s built-in authentication method.</para>
    170174
    171175</sect3>
    172176
    173 <sect3><title>4.  Starting the server</title>
    174 <para>There are a couple of ways to start <command>svnserve</command>.  The
    175 most common way is to start it as an <application>inetd</application> or
    176 <application>xinetd</application> process.  Alternately, you can use a
     177<sect3><title>4. Starting the server</title>
     178<para>There are a couple of ways to start <command>svnserve</command>. The
     179most common way is to start it as an <command>inetd</command> or
     180<command>xinetd</command> process. Alternately, you can use a
    177181bootscript to start the service at startup.</para>
    178182
     
    182186<command>svnserve</command>.</para></note>
    183187
    184 <para>If you use <application>inetd</application>, add a line to your
     188<para>If you use <command>inetd</command>, add a line to
    185189<filename>/etc/inetd.conf</filename> using the following commands:</para>
    186190
     
    189193<command>EOF</command></userinput></screen>
    190194
    191 <para>If you use <application>xinetd</application>, add the following
    192 lines to <filename>/etc/xinetd.conf</filename> file:</para>
     195<para>If you use <command>xinetd</command>, add the following
     196lines to the <filename>/etc/xinetd.conf</filename> file:</para>
    193197
    194198<screen><userinput><command>cat &gt;&gt; /etc/xinetd.conf &lt;&lt; "EOF"</command>
Note: See TracChangeset for help on using the changeset viewer.