Here's a patch to install.xml to deal with upgrading. Feedback welcome.
Index: install.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/install.xml,v
retrieving revision 1.20
diff -u -r1.20 install.xml
--- install.xml 27 Jun 2003 18:53:03 -0000 1.20
+++ install.xml 24 Jul 2003 19:26:45 -0000
@@ -21,6 +21,10 @@
to create an environment that looks like many other Open Source
projects.</p>
+ <p>If you upgrading from one minor version to the next (for
+ example, 2.0.50 to 2.0.51), please skip down to the <a
+ href="#upgrading">upgrading</a> section.</p>
+
</summary>
<seealso><a href="invoking.html">Starting Apache</a></seealso>
@@ -297,7 +301,7 @@
<dd>Header file search directories ("<code>-I<em>dir</em></code>").</dd>
- <dt><code>TARGET=...</code> [Default: <code>apache</code>]</dt>
+ <dt><code>TARGET=...</code> [Default: <code>httpd</code>]</dt>
<dd>Name of the executable which will be built.</dd>
@@ -547,7 +551,7 @@
<section id="install"><title>Install</title>
- <p>Now its time to install the package under the configured
+ <p>Now it's time to install the package under the configured
installation <em>PREFIX</em> (see <code>--prefix</code> option
above) by running:</p>
@@ -588,6 +592,40 @@
running:</p>
<example>$ <em>PREFIX</em>/bin/apachectl stop</example>
+</section>
+
+<section id="upgrading"><title>Upgrading</title>
+
+ <p>Upgrading from one minor version to the next is easy. The
+ <code>make install</code> process will not overwrite any of your
+ existing documents or your configuration file. In addition, the
+ developers make every effort to avoid incompatible changes in the
+ <code>configure</code> options, run-time configuration, or the
+ module API between minor versions. So for example, in a change
+ from 2.0.58 to 2.0.59, you should be able to use an identical
+ <code>configure</code> command line, an identical configuration
+ file, and all of your modules should continue to work. (This is
+ only valid for versions after 2.0.41; earlier versions have
+ incompatible changes.)</p>
+
+ <p>If you kept your source tree from your last installation,
+ upgrading is even easier. The file <code>config.nice</code>
+ in the root of the source tree contains the exact <code>configure</code>
+ command line used to configure the source tree. Then to
+ upgrade from one version to the next, you need only copy the
+ <code>config.nice</code> file to the source tree of the new
+ version, edit it to make any desired changes, and then run:</p>
+
+ <example>
+ $ ./config.nice<br />
+ $ make<br />
+ $ make install<br />
+ $ <em>PREFIX</em>/bin/apachectl stop<br />
+ $ <em>PREFIX</em>/bin/apachectl start<br />
+ </example>
+
+ <p>Of course, you should always test any new version in your
+ environment before putting it into production.</p>
</section>
</manualpage>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
