Changeset cf5c43f3 for server

Timestamp:

04/07/2006 01:56:59 AM (18 years ago)

Author:

Randy McMurchy <randy@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.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, 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/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

6c8659b

Parents:

c04745b

Message:

Added a parameter to the Subversion build commands to disable the use of Berkeley DB; also added commands to fix the improper permissions on the installed documentation

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

File:

• server/other/svnserver.xml (modified) (5 diffs)

server/other/svnserver.xml

@@ -21 +21 @@
     <para>This section will describe how to set up, administer and secure
     a <application>Subversion</application> server.</para>
+
+    <note>
+      <para>The default build instructions for
+      <application>Subversion</application> disabled the
+      <application>Berkeley DB</application> repository back-end due to the
+      errors encountered in the test suite while building the
+      <xref linkend="subversion"/> package. This should not present a
+      functionality issue as the FSFS repository back-end is now the default,
+      and recommended by the <application>Subversion</application> development
+      team.</para>
+
+      <para>If you have existing repositories based on a
+      <application>Berkeley DB</application> back-end and you followed the
+      BLFS instructions for building <application>Subversion</application>,
+      you'll need to dump the databases, create new repositories using the
+      FSFS back-end, then then reload the data into the new repositories.
+      Instructions for performing these operations can be found at <ulink
+      url="http://svnbook.red-bean.com/en/1.1/ch05s03.html#svn-ch-5-sect-3.5"/>.
+      </para>
+    </note>
 
     <bridgehead renderas="sect3">Subversion Server Dependencies</bridgehead>
@@ -99 +119 @@
       FSFS and BDB, see <ulink
       url="http://svnbook.red-bean.com/svnbook-1.1/ch05.html#svn-ch-5-sect-1.2.A"/>.
-      Optionally you can pass <option>bdb</option> in place of
-      <option>fsfs</option> in the following command to create a
-      BerkeleyDB data-store.</para>
+      </para>
 
       <para>Create a new <application>Subversion</application> repository with
       the following commands:</para>
 
-<screen role="root"><userinput>install -d -m0755 /srv &amp;&amp;
-install -d -m0755 -o svn -g svn /srv/svn/repositories &amp;&amp;
+<screen role="root"><userinput>install -v -m 0755 -d /srv &amp;&amp;
+install -v -m 0755 -o svn -g svn -d /srv/svn/repositories &amp;&amp;
 svnadmin create --fs-type fsfs /srv/svn/repositories/svntest</userinput></screen>
 
-      <para>Now that the repository is created, we need to populate it
+      <para>Now that the repository is created, it should be populated with
       with something useful. You'll need to have a predefined directory
-      layout setup exactly as you want your repository to look. For
+      layout set up 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
@@ -134 +152 @@
     file:///srv/svn/repositories/svntest</userinput></screen>
 
-      <para>Now go ahead and change owner and group information on the
+      <para>Now change owner and group information on the
       repository, and add an unprivileged user to the
       <systemitem class="groupname">svn</systemitem> and
@@ -163 +181 @@
       files. This avoids locking out other users from the repository.</para>
 
-      <para>Now, go ahead and return to an unprivileged user account, and take a
-      look at your new repository using <command>svnlook</command>:</para>
+      <para>Now, return to an unprivileged user account, and take a
+      look at the new repository using <command>svnlook</command>:</para>
 
 <screen><userinput>svnlook tree /srv/svn/repositories/svntest/</userinput></screen>
@@ -257 +275 @@
 EOF</userinput></screen>
 
-      <para>Finally, if you wish to simply start the sever at
+      <para>Finally, if you wish to simply start the server at
       startup, install the svn bootscript included in the
       <xref linkend="bootscripts"/> package.</para>