On Sat, 2005-04-16 at 06:56 +0100, Elfyn McBratney wrote:
> As I'm sure many of you will know, the updated apache and associated ebuilds
> (so-called apache refresh) have caused a number of problems since coming out
> of package.mask and going into testing. As a result, we have a number of
> packages that simply do not function with the updated apache ebuilds,
> rendering testing (on the apache side of things) broken.
Yes, this has gotten very annoying.
> A number of people have suggested putting these updated ebuilds back into
> package.mask, or lessening the impact of the upgrade from current stable
> apache to the new ~arch apache. So, I would like to solicit advice from the
> developer community as to how we can rectify this.
> The way I see it, we have three options:
> - package.mask (downgrades for those early adopters)
> - keep the same layout (/etc/apache2/conf, etc.) and wait until 2.2 is out to
> change it
> - have the newer apache ebuilds migrate from old-style to new-style config
> (very hard to do, but possible)
I say at the very least package.mask it. Testing is supposed to be able
to compile and work, not half work and test. There's a reason we have a
package.mask, please use it! To me, it makes more sense to push these
changes in the next major release of apache (2.1/2.2). 2.0.x should be
kept as is since a lot of people are using that now and any change
midway through the release would cause a lot of havoc.
So far, most of the changes don't seem to be backward compatible with
each other. Right now you can't make a module that will work for either
variation of the layout without hacking it badly. To me, thats bad
especially since the new layout isn't in package.mask.
I just fear if we continue to push these changes on the current 2.0.x
line will continue to piss off a lot of people.
Lance Albertson <email@example.com>
Gentoo Infrastructure | Operations Manager
Public GPG key: <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742