httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject cvs commit: httpd-2.0/docs/manual install.xml install.html.en
Date Mon, 28 Jul 2003 14:17:47 GMT
slive       2003/07/28 07:17:46

  Modified:    docs/manual Tag: APACHE_2_0_BRANCH install.xml
                        install.html.en
  Log:
  Backport minor version upgrade instructions.
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.11.2.9  +53 -2     httpd-2.0/docs/manual/install.xml
  
  Index: install.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/install.xml,v
  retrieving revision 1.11.2.8
  retrieving revision 1.11.2.9
  diff -u -d -b -u -r1.11.2.8 -r1.11.2.9
  --- install.xml	30 Jun 2003 19:25:24 -0000	1.11.2.8
  +++ install.xml	28 Jul 2003 14:17:45 -0000	1.11.2.9
  @@ -21,6 +21,10 @@
       to create an environment that looks like many other Open Source
       projects.</p>
   
  +    <p>If you are 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>
   
  @@ -589,5 +593,52 @@
   
   <example>$ <em>PREFIX</em>/bin/apachectl stop</example>
   </section>
  +<section id="upgrading"><title>Upgrading</title>
  +
  +    <p>The first step in upgrading is to read the release announcement
  +    and the file <code>CHANGES</code> in the source distribution to
  +    find any changes that may affect your site.  When changing between
  +    major releases (for example, from 1.3 to 2.0 or from 2.0 to 2.2),
  +    there will likely be major differences in the compile-time and
  +    run-time configuration that will require manual adjustments.  All
  +    modules will also need to be upgraded to accomodate changes in the
  +    module API.</p>
   
  +    <p>Upgrading from one minor version to the next (for example, from
  +    2.0.55 to 2.0.57) is easier.  The <code>make install</code>
  +    process will not overwrite any of your existing documents, log
  +    files, or configuration files.  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.  In most cases 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 the source tree from your last installation,
  +    upgrading is even easier.  The file <code>config.nice</code> in
  +    the root of the old source tree contains the exact
  +    <code>configure</code> command line that you 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>
  +
  +    <note type="warning">You should always test any new version in your
  +    environment before putting it into production.  For example, you
  +    can install and run the new version along side the old one by
  +    using a different <code>--prefix</code> and a
  +    different port (by adjusting the <directive
  +    module="mpm_common">Listen</directive> directive) to test for any
  +    incompatibilities before doing the final upgrade.</note>
  +</section>
   </manualpage>
  
  
  
  1.56.2.9  +54 -2     httpd-2.0/docs/manual/install.html.en
  
  Index: install.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/install.html.en,v
  retrieving revision 1.56.2.8
  retrieving revision 1.56.2.9
  diff -u -d -b -u -r1.56.2.8 -r1.56.2.9
  --- install.html.en	30 Jun 2003 22:17:41 -0000	1.56.2.8
  +++ install.html.en	28 Jul 2003 14:17:45 -0000	1.56.2.9
  @@ -38,6 +38,9 @@
       to create an environment that looks like many other Open Source
       projects.</p>
   
  +    <p>If you are 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>
  +
   </div>
   <div id="quickview"><ul id="toc"><li><img alt="" src="./images/down.gif"
/> <a href="#overview">Overview for the
       impatient</a></li>
  @@ -49,6 +52,7 @@
   <li><img alt="" src="./images/down.gif" /> <a href="#install">Install</a></li>
   <li><img alt="" src="./images/down.gif" /> <a href="#customize">Customize</a></li>
   <li><img alt="" src="./images/down.gif" /> <a href="#test">Test</a></li>
  +<li><img alt="" src="./images/down.gif" /> <a href="#upgrading">Upgrading</a></li>
   </ul><h3>See also</h3><ul class="seealso"><li><a href="invoking.html">Starting
Apache</a></li><li><a href="stopping.html">Stopping and Restarting</a></li></ul></div>
   <div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif"
/></a></div>
   <div class="section">
  @@ -316,7 +320,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>
   
  @@ -562,7 +566,7 @@
   <div class="section">
   <h2><a name="install" id="install">Install</a></h2>
   
  -    <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>
   
  @@ -599,6 +603,54 @@
       running:</p>
   
   <div class="example"><p><code>$ <em>PREFIX</em>/bin/apachectl
stop</code></p></div>
  +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif"
/></a></div>
  +<div class="section">
  +<h2><a name="upgrading" id="upgrading">Upgrading</a></h2>
  +
  +    <p>The first step in upgrading is to read the release announcement
  +    and the file <code>CHANGES</code> in the source distribution to
  +    find any changes that may affect your site.  When changing between
  +    major releases (for example, from 1.3 to 2.0 or from 2.0 to 2.2),
  +    there will likely be major differences in the compile-time and
  +    run-time configuration that will require manual adjustments.  All
  +    modules will also need to be upgraded to accomodate changes in the
  +    module API.</p>
  +
  +    <p>Upgrading from one minor version to the next (for example, from
  +    2.0.55 to 2.0.57) is easier.  The <code>make install</code>
  +    process will not overwrite any of your existing documents, log
  +    files, or configuration files.  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.  In most cases 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 the source tree from your last installation,
  +    upgrading is even easier.  The file <code>config.nice</code> in
  +    the root of the old source tree contains the exact
  +    <code>configure</code> command line that you 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>
  +
  +    <div class="example"><p><code>
  +    $ ./config.nice<br />
  +    $ make<br />
  +    $ make install<br />
  +    $ <em>PREFIX</em>/bin/apachectl stop<br />
  +    $ <em>PREFIX</em>/bin/apachectl start<br />
  +    </code></p></div>
  +
  +    <div class="warning">You should always test any new version in your
  +    environment before putting it into production.  For example, you
  +    can install and run the new version along side the old one by
  +    using a different <code>--prefix</code> and a
  +    different port (by adjusting the <code class="directive"><a href="./mod/mpm_common.html#listen">Listen</a></code>
directive) to test for any
  +    incompatibilities before doing the final upgrade.</div>
   </div></div>
   <div class="bottomlang">
   <p><span>Available Languages: </span><a href="./de/install.html" hreflang="de"
rel="alternate" title="Deutsch">&nbsp;de&nbsp;</a> |
  
  
  

Mime
View raw message