Re: [gentoo-server] Stabilization of new-style Apache

[Ben Munat <bent@munat.com>]

Well, well... yet another false alarm...

Indeed, a new ebuild of Apache was unmasked today. However, it is not -- yet again -- this 
major re-working of the apache layout that we've been hearing about for over nine months now.

Sigh.

b


Michael Stewart (vericgar) wrote:
> The Gentoo Apache Team is pleased to announce the stabilizing of package
> updates that have been in the works for over a year. Some of the major
> changes include:
> 
>  - New configuration and configuration locations to more closely match
>    upstream and reduce confusion for users coming from other
>    distributions.
>  - Modules now use a centralized eclass that builds, installs, and
>    displays standard information on enabling the module. This allows
>    easier maintenance of existing modules, and allows us to more rapidly
>    develop ebuilds for modules that are not yet in the tree.
>  - Expanded USE flags to let you choose which MPM is compiled.
>  - A new gentoo-webroot that will eventually provide a gentoo-themed
>    icon-set, error documents, and default website. This has been put in
>    it's own package, and includes a USE-flag to not install the
>    gentoo-webroot into /var/www/localhost - useful if you put your own
>    website there.
>  - And much more, including the fixing of many many bugs.
> 
> These changes will stabilized on Sunday, September 18th. These changes
> have been throughly tested and given a thumbs up by many many users.
> They also allow you to use the new php (including support for php5)
> ebuilds when they become fully available.
> 
> Because of these changes and improvements, when you upgrade to the new
> revision of Apache, you will need to take care of some things. These are
> fully documented in our Upgrading Apache document [1], but in
> summary, this is what you will need to do:
> 
>  - Merge any customizations that you have made to the Apache
>    configuration into the new configuration at /etc/apache2/httpd.conf
>    (The configuration file location has changed). Note that the init
>    script for apache checks for a configuration in the old location and
>    refuses to start if you haven't moved/removed it - this is to avoid
>    the possibility of moving to a configuration that isn't right for
>    your machine.
>  - Update any modules that you used to revisions that support the new
>    eclass. Older modules will not work due to location changes.
>  - Restart Apache
> 
> We have done our best to make it easy to migrate, but if you have
> problems, feel free to visit us in #gentoo-apache on irc.freenode.net or
> on our mailing list gentoo-web-user@gentoo.org and we'll be glad to
> help.
> 
> Thanks,
> The Gentoo Apache Team
> 
> [1] http://www.gentoo.org/doc/en/apache-upgrading.xml
> 
-- 
gentoo-server@gentoo.org mailing list