public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Parpart <trapni@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] net-www/apache testing request (marking stable anytime soon)
Date: Sun, 10 Apr 2005 18:43:13 +0200	[thread overview]
Message-ID: <200504101843.15345.trapni@gentoo.org> (raw)
In-Reply-To: <1113144935.4536.2.camel@matrix.brianandsara.net>

[-- Attachment #1: Type: text/plain, Size: 2102 bytes --]

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 #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-04-10 16:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-09 13:59 [gentoo-dev] net-www/apache testing request (marking stable anytime soon) Christian Parpart
2005-04-10 14:55 ` Brian Jackson
2005-04-10 16:43   ` Christian Parpart [this message]
2005-04-10 17:18     ` Jason Wever
2005-04-11  1:38       ` Christian Parpart
2005-04-11  1:43         ` Jason Wever
2005-04-11 17:55           ` Stuart Herbert
2005-04-11 18:07             ` Jason Wever
2005-04-12 18:28               ` Paul de Vrieze
2005-04-12 18:47                 ` Ciaran McCreesh
2005-04-14 22:37                   ` Stuart Herbert
2005-04-12 20:21                 ` Jason Wever
2005-04-14 22:35               ` Stuart Herbert
2005-04-11 20:19             ` Christian Parpart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200504101843.15345.trapni@gentoo.org \
    --to=trapni@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox