| 1 |
The Gentoo Apache Team is pleased to announce the unmasking of package |
| 2 |
updates that have been in the works for months. Some of the major |
| 3 |
changes include: |
| 4 |
|
| 5 |
- New configuration and configuration locations to more closely match |
| 6 |
upstream and reduce confusion for users coming from other distributions. |
| 7 |
- Modules now use a centralized eclass that builds, installs, and |
| 8 |
displays standard information on enabling the module. This allows easier |
| 9 |
maintenance of existing modules, and allows us to more rapidly develop |
| 10 |
ebuilds for modules that are not yet in the tree. |
| 11 |
- Expanded USE flags to customize your apache installation now let you |
| 12 |
choose multiple MPMs to build and make it easy to switch between them. |
| 13 |
- A new gentoo-webroot that will eventually provide a gentoo-themed |
| 14 |
icon-set, error documents, and default website. This has been put in |
| 15 |
it's own package, and includes a USE-flag to not install the |
| 16 |
gentoo-webroot into /var/www/localhost - useful if you put your own |
| 17 |
website there. |
| 18 |
- And much more, including the fixing of many many bugs |
| 19 |
|
| 20 |
These changes will shortly be available for users running unstable ~arch |
| 21 |
KEYWORDS). We believe our changes to be safe for general consumption as |
| 22 |
we have been testing them for several months and they have been |
| 23 |
available, albeit package masked, for over a month. |
| 24 |
|
| 25 |
Because of these changes and improvements, when you upgrade to the new |
| 26 |
revision of Apache, you will need to take care of some things. These are |
| 27 |
fully documented in our Apache Package Refresh Document [1], but in |
| 28 |
summary, this is what you will need to do: |
| 29 |
|
| 30 |
- Merge any customizations that you have made to the Apache |
| 31 |
configuration into the new configuration at /etc/apache2/httpd.conf (The |
| 32 |
configuration file location has changed). Note that the init script for |
| 33 |
apache checks for a configuration in the old location and refuses to |
| 34 |
start if you haven't moved/removed it - this is to avoid the possibility |
| 35 |
of moving to a configuration that isn't right for your machine. |
| 36 |
- Update any modules that you used to revisions that support the new |
| 37 |
eclass. Older modules will not work due to location changes. |
| 38 |
- Restart Apache |
| 39 |
|
| 40 |
We have done our best to make it easy to migrate, but if you have |
| 41 |
problems, feel free to visit us in #gentoo-apache on irc.freenode.net or |
| 42 |
on our mailing list gentoo-web-user@g.o and we'll be glad to help. |
| 43 |
|
| 44 |
|
| 45 |
If you are a package maintainer that has a package that uses Apache in |
| 46 |
any way, you should check the documentation[1] and modify your ebuild to |
| 47 |
make use of new Apache paths. We have tried to file bugs against all |
| 48 |
packages that need changes, but we may have missed some. |
| 49 |
|
| 50 |
|
| 51 |
Thanks, |
| 52 |
The Gentoo Apache Team |
| 53 |
|
| 54 |
[1] http://dev.gentoo.org/~vericgar/doc/apache-package-refresh.html |
| 55 |
|
| 56 |
|
| 57 |
-- |
| 58 |
Michael Stewart vericgar@g.o |
| 59 |
Gentoo Developer http://dev.gentoo.org/~vericgar |
| 60 |
|
| 61 |
GnuPG Key ID 0x08614788 available on http://pgp.mit.edu |
| 62 |
-- |
| 63 |
-- |
| 64 |
gentoo-dev@g.o mailing list |
Archives