svn commit - mysqldoc@docsrva: r586 - in trunk: . refman-5.1

[paul]

Author: paul
Date: 2005-12-18 01:35:15 +0100 (Sun, 18 Dec 2005)
New Revision: 586

Log:
 r4893@frost:  paul | 2005-12-17 18:34:55 -0600
 Add missing tags.


Modified:
   trunk/
   trunk/refman-5.1/extending-mysql.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4879
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1694
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4893
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1694

Modified: trunk/refman-5.1/extending-mysql.xml
===================================================================
--- trunk/refman-5.1/extending-mysql.xml	2005-12-17 22:47:50 UTC (rev 585)
+++ trunk/refman-5.1/extending-mysql.xml	2005-12-18 00:35:15 UTC (rev 586)
@@ -2090,18 +2090,21 @@
           <listitem>
             <para>
               Compile the plugin library as a shared library and install
-              it in the plugin directory. The procedure for compiling
-              shared objects varies from system to system. If you build
-              your library using the GNU autotools,
-              <command>libtool</command> should be able to generate the
-              correct compilation commands for your system. If the
-              library is named <literal>mypluglib</literal>, you should
-              end up with a shared object file that has a name something
-              like <filename>libmypluglib.so</filename>. (The filename
-              might have a different extension on your system.)
+              it in the plugin directory.
             </para>
 
             <para>
+              The procedure for compiling shared objects varies from
+              system to system. If you build your library using the GNU
+              autotools, <command>libtool</command> should be able to
+              generate the correct compilation commands for your system.
+              If the library is named <literal>mypluglib</literal>, you
+              should end up with a shared object file that has a name
+              something like <filename>libmypluglib.so</filename>. (The
+              filename might have a different extension on your system.)
+            </para>
+
+            <para>
               The location of the plugin directory where you should
               install the library is given by the
               <literal>plugin_dir</literal> system variable. For