From: "Xavier Neys" <neysx@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: apache-upgrading.xml
Date: Thu, 29 Sep 2005 09:28:21 +0000 [thread overview]
Message-ID: <200509290921.j8T9L9RJ017667@robin.gentoo.org> (raw)
neysx 05/09/29 09:28:21
Modified: xml/htdocs/doc/en apache-upgrading.xml
Log:
#107567 Remove package.keyword stuff to reflect new stable apache
Revision Changes Path
1.3 +4 -57 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.3&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.3&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/apache-upgrading.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo
Index: apache-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/apache-upgrading.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- apache-upgrading.xml 1 Aug 2005 15:52:23 -0000 1.2
+++ apache-upgrading.xml 29 Sep 2005 09:28:21 -0000 1.3
@@ -1,5 +1,7 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/apache-upgrading.xml,v 1.3 2005/09/29 09:28:21 neysx Exp $ -->
+
<guide link="apache-upgrading.xml" lang="en">
<title>Upgrading Apache</title>
@@ -16,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.2</version>
-<date>2005-08-01</date>
+<version>2.3</version>
+<date>2005-09-29</date>
<chapter>
<title>Introduction</title>
@@ -30,7 +32,6 @@
everything the Apache herd is responsible for difficult:
</p>
-
<ul>
<li>
The configuration that came with Gentoo was dramatically different from
@@ -61,7 +62,6 @@
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
@@ -90,7 +90,6 @@
package.
</p>
-
<pre caption="Finding packages to update">
$ <i>equery depends net-www/apache</i>
[ Searching for packages depending on net-www/apache... ]
@@ -108,76 +107,29 @@
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 \
@@ -193,7 +145,6 @@
# <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>
@@ -219,7 +170,6 @@
have reconfigured apache using the new paths.
</p>
-
<note>
Many modules that used to be enabled by default are now disabled. If they are
apache built-in modules, then uncomment the appropriate line in httpd.conf.
@@ -227,18 +177,15 @@
add the name to <path>/etc/conf.d/apache{|2}</path> to enable it.
</note>
-
<p>
Now you may restart apache.
</p>
-
<pre caption="Restarting apache">
# <i>/etc/init.d/apache stop</i>
# <i>/etc/init.d/apache start</i>
</pre>
-
<p>
If you run into any problems check the <uri
link="/doc/en/apache-troubleshooting.xml">Apache Troubleshooting Guide</uri>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2005-09-29 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 9:28 Xavier Neys [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-05 19:53 [gentoo-doc-cvs] cvs commit: apache-upgrading.xml Camille Huot
2008-03-05 19:52 Camille Huot
2007-12-12 2:44 Joshua Saddler
2007-07-29 21:36 Josh Saddler
2006-04-12 17:47 Josh Saddler
2005-08-01 15:17 Sven Vermeulen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200509290921.j8T9L9RJ017667@robin.gentoo.org \
--to=neysx@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox