swift 05/08/01 15:17:11 Modified: xml/htdocs/doc/en metadoc.xml Added: xml/htdocs/doc/en apache-upgrading.xml Log: #99539 - Adding Apache upgrading document
Revision Changes Path 1.91 +6 -1 xml/htdocs/doc/en/metadoc.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml?rev=1.91&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml?rev=1.91&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml.diff?r1=1.90&r2=1.91&cvsroot=gentoo Index: metadoc.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v retrieving revision 1.90 retrieving revision 1.91 diff -u -r1.90 -r1.91 --- metadoc.xml 1 Aug 2005 14:49:01 -0000 1.90 +++ metadoc.xml 1 Aug 2005 15:17:11 -0000 1.91 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.90 2005/08/01 14:49:01 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.91 2005/08/01 15:17:11 swift Exp $ --> <!DOCTYPE metadoc SYSTEM "/dtd/metadoc.dtd"> <metadoc lang="en"> @@ -360,6 +360,7 @@ <file id="shb-tight">/doc/en/security/shb-tight.xml</file> <file id="shb-uptodate">/doc/en/security/shb-uptodate.xml</file> <file id="apache-troubleshooting">/doc/en/apache-troubleshooting.xml</file> + <file id="apache-upgrading">/doc/en/apache-upgrading.xml</file> </files> <docs> <doc id="name-logo"> @@ -984,5 +985,9 @@ <memberof>sysadmin_specific</memberof> <fileid>apache-troubleshooting</fileid> </doc> + <doc id="apache-upgrading"> + <memberof>sysadmin_specific</memberof> + <fileid>apache-upgrading</fileid> + </doc> </docs> </metadoc> 1.1 xml/htdocs/doc/en/apache-upgrading.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/apache-upgrading.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/apache-upgrading.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo Index: apache-upgrading.xml =================================================================== <?xml version='1.0' encoding="UTF-8"?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="apache-upgrading.xml" lang="en"> <title>Upgrading Apache</title> <author title="Author"> <mail link="[EMAIL PROTECTED]">Michael Stewart</mail> </author> <abstract> This document describes the procedure end-users should follow to safely upgrade their apache installation. </abstract> <!-- The content of this document is licensed under the CC-BY-SA license --> <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> <version>2.1</version> <date>2005-08-01</date> <chapter> <title>Introduction</title> <section> <body> <p> The state of Apache and it's modules in Gentoo was becoming dismal. There were a number of problems that caused support problems and made maintaining everything the Apache herd is responsible for difficult: </p> <ul> <li> The configuration that came with Gentoo was dramatically different from the upstream configuration that most users expect </li> <li> Many modules used similar code, but all did things their own way </li> <li> Most modules weren't maintained very well - mostly because of the large number of modules available </li> <li>Modules didn't have a configuration standard</li> <li> Some modules could support both versions of Apache, but the ebuilds didn't handle that </li> <li> Choices available in Apache were not available for Gentoo users (for example MPMs) </li> <li>Bugs for Apache were stacking up</li> </ul> <p> The solution? The Apache herd was expanded, adding several new members, who worked together to create an eclass, update all the modules and fix a number of bugs. </p> <p> This document details how to upgrade without breaking your system. If you are a developer or would like to know what we changed, or how ebuilds need to be modified to take advantage of our eclass, then check the <uri link="/proj/en/developer.xml">Apache Developer Reference</uri>. </p> </body> </section> </chapter> <chapter id="upgrade"> <title>Upgrade Instructions</title> <section> <body> <p> We have made many changes to how Apache works within Gentoo. Every package that is directly related to Apache needs to be updated and some things that worked previously will no longer work. </p> <p> First you need to figure out what packages you need to upgrade. You can do this using the <c>equery</c> tool, part of the <c>app-portage/gentoolkit</c> package. </p> <pre caption="Finding packages to update"> $ <i>equery depends net-www/apache</i> [ Searching for packages depending on net-www/apache... ] dev-db/phpmyadmin-2.5.6 dev-php/mod_php-4.3.10 dev-php/phpsysinfo-2.1-r2 net-www/mod_bandwidth-2.0.5 net-www/mod_layout-4.0.1a net-www/mod_ldap_userdir-1.1.4 net-www/mod_loopback-1.04 net-www/mod_mp3-0.40 net-www/mod_random-2.0 net-www/mod_throttle-3.1.2-r1 net-www/mod_watch-3.18 www-apps/viewcvs-0.9.2_p20030430 </pre> <impo> The packages you have installed may be vastly different, make sure you run this command for yourself. </impo> <warn> There are some modules and packages that depend on Apache that have not yet been updated. Please <uri link="http://bugs.gentoo.org";>search bugzilla</uri> for any critical packages that you use with Apache. </warn> <p> Many webapps aren't affected in any way as most use the <c>webapp</c> eclass which takes care of installing them correctly. You may want to check to see if there is a new revision. </p> <!-- Remove between this line and the next when new style goes stable --> <p> As all the packages that support our changes are still in unstable, to be able to use them you will need to add all the packages you want to upgrade (see above) as well as the following to <path>/etc/portage/package.keywords</path>. </p> <note> <path>/etc/portage</path> may not exist, please create it, as well as the files inside it. </note> <pre caption="Additions to /etc/portage/package.keywords"> <comment>(If you are using Apache 1.3)</comment> =net-www/apache-1* net-www/gentoo-webroot-default <comment>(If you want to use lingerd with Apache 1.3)</comment> net-www/lingerd <comment>(If you are using Apache 2.0)</comment> net-www/apache dev-libs/apr dev-libs/apr-util net-www/gentoo-webroot-default <comment>(Include all others that you need to upgrade as well)</comment> dev-php/mod_php net-www/mod_bandwidth net-www/mod_layout net-www/mod_ldap_userdir net-www/mod_loopback net-www/mod_mp3 net-www/mod_random net-www/mod_throttle net-www/mod_watch </pre> <!-- Remove between this line and the previous when new style goes stable --> <p> As we have added some new USE-flags, you may want to review them and add appropriate lines to <path>/etc/portage/package.use</path>. See <uri link="#use">Apache supported USE-flags</uri> for more details. </p> <pre caption="Checking USE flag settings and rebuild"> <comment>(Check the USE-flags and needed updates)</comment> # <i>emerge --pretend --verbose --update --newuse --deep apache subversion \ mod_php mod_bandwidth mod_layout mod_ldap_userdir mod_loopback mod_mp3 \ mod_random mod_throttle mod_watch</i> <comment>(Update the packages)</comment> # <i>emerge --verbose --update --newuse --deep apache subversion mod_php \ mod_bandwidth mod_layout mod_ldap_userdir mod_loopback mod_mp3 mod_random \ mod_throttle mod_watch</i> <comment>(It may be easier to just update world instead of the above)</comment> # <i>emerge --ask --verbose --update --newuse --deep world</i> </pre> <p> Now you need to reconfigure Apache and its modules. Start by using <c>etc-update</c> or <c>dispatch-conf</c> to update the <path>/etc/init.d</path> -- [email protected] mailing list
