1 |
Hi Folks, |
2 |
|
3 |
As I'm sure many of you will know, the updated apache and associated ebuilds |
4 |
(so-called apache refresh) have caused a number of problems since coming out |
5 |
of package.mask and going into testing. As a result, we have a number of |
6 |
packages that simply do not function with the updated apache ebuilds, |
7 |
rendering testing (on the apache side of things) broken. |
8 |
|
9 |
Currently, we have at least two (possibly three) weeks worth of work to do |
10 |
before we can mark things stable, so these breakages will likely exist until |
11 |
then. |
12 |
|
13 |
A number of people have suggested putting these updated ebuilds back into |
14 |
package.mask, or lessening the impact of the upgrade from current stable |
15 |
apache to the new ~arch apache. So, I would like to solicit advice from the |
16 |
developer community as to how we can rectify this. |
17 |
|
18 |
The way I see it, we have three options: |
19 |
- package.mask (downgrades for those early adopters) |
20 |
- keep the same layout (/etc/apache2/conf, etc.) and wait until 2.2 is out to |
21 |
change it |
22 |
- have the newer apache ebuilds migrate from old-style to new-style config |
23 |
(very hard to do, but possible) |
24 |
|
25 |
Personally, I'm for package.masking, heh. Let the flames commence. |
26 |
|
27 |
Best, |
28 |
Elfyn |
29 |
|
30 |
-- |
31 |
Elfyn McBratney http://beu.merseine.nu/ |
32 |
beu/irc.freenode.net http://dev.gentoo.org/~beu/ |
33 |
+------------O.o--------------------- http://dev.gentoo.org/~beu/pubkey.asc |
34 |
|
35 |
PGP Key ID: 0x69DF17AD |
36 |
PGP Key Fingerprint: |
37 |
DBD3 B756 ED58 B1B4 47B9 B3BD 8D41 E597 69DF 17AD |