- 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 customize your apache installation now let you choose multiple MPMs to build and make it easy to switch between them.
- 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 shortly be available for users running unstable ~arch KEYWORDS). We believe our changes to be safe for general consumption as we have been testing them for several months and they have been available, albeit package masked, for over a month.
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 Apache Package Refresh 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 [EMAIL PROTECTED] and we'll be glad to help.
If you are a package maintainer that has a package that uses Apache in any way, you should check the documentation[1] and modify your ebuild to make use of new Apache paths. We have tried to file bugs against all packages that need changes, but we may have missed some.
Thanks, The Gentoo Apache Team
[1] http://dev.gentoo.org/~vericgar/doc/apache-package-refresh.html
-- Michael Stewart [EMAIL PROTECTED] Gentoo Developer http://dev.gentoo.org/~vericgar
GnuPG Key ID 0x08614788 available on http://pgp.mit.edu -- -- [email protected] mailing list
