On Sunday 10 April 2005 4:55 pm, Brian Jackson wrote:
> How about not breaking apache? 

We did not break apache, we broke *binary compatibility* within apache.
Are you aware of *why* we decided to break binary compatibility?
Well, if not, I can say we did so to provide LFS to the end-users.
You might not need it, but for sure, others will be very happy about. So, 
please before just asking this, also consider the benifits from it.

Of course, we did not wanna push nearly-everyones little blindly executed 
`emerge -uvD world` into hell. But everyone makes mistakes, so including me. 
sorry for that, though, we got almost every complain fixed already. That's 
why we're requesting for testing, for being sure, going stable won't shoot 
anyone into his foot again.

Finally, the eclass updates have been a BIG must to simplify maintaince in a 
long term. So, we could of course have introduced just yet another eclass 
resisting parallel to the old one - just to have worked around this breakage 
as well. Yeah, we learn all the time :)

> I was a little beyond pissed when I had 
> to sit there for 2 hours trying to figure out why my apache was broken,
> and who was going to get put on my list of being kicked in the junk.
> Just for some stupid config file changes. 

does it work now? when did you upgrade? what problems did you run in? please 
feedback us. That's what we was calling for ;-)

> I find it very hard to believe 
> you guys couldn't come up with a better way to do it. Even if that means
> doing evil stuff in one of the stages that isn't sandboxed.

We thought about doing so but decided against. At least my reason was, because 
this would be a bloody hell and a no-go in a garrantied clean config merge.

I advice everyone to configure their new apache files (httpd.conf for 
commonapache/apache.conf) from scratch.

Regards,
Christian Parpart.

-- 
the following rfc contains how to quote on lists like this:
Netiquette: http://www.ietf.org/rfc/rfc1855.txt
 17:57:59 up 18 days,  7:04,  0 users,  load average: 0.28, 0.31, 0.35

Attachment: pgprALEbGGY3f.pgp
Description: PGP signature

Reply via email to