public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lance Albertson <ramereth@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Moving the updated apache and associated ebuilds back into package.mask
Date: Sat, 16 Apr 2005 01:10:31 -0500	[thread overview]
Message-ID: <1113631832.10461.9.camel@mirage.ramereth.lan> (raw)
In-Reply-To: <200504160656.43452@zippy.emcb.local>

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

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.

[snip]

> 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.

Cheers,

-- 
Lance Albertson <ramereth@gentoo.org>
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

ramereth/irc.freenode.net

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-16  5:56 [gentoo-dev] Moving the updated apache and associated ebuilds back into package.mask Elfyn McBratney
2005-04-16  6:10 ` Lance Albertson [this message]
2005-04-16 12:38 ` Paul Varner
2005-04-19 19:31   ` Paul de Vrieze
2005-04-19 19:45     ` Elfyn McBratney
2005-04-19 20:51       ` Paul de Vrieze
2005-04-20  7:36         ` Christian Parpart
2005-04-20  8:59           ` Paul de Vrieze
2005-04-20 15:25             ` Christian Parpart
2005-04-21 13:13               ` Paul de Vrieze
2005-04-20 12:14           ` Lance Albertson
2005-04-20 15:22             ` Christian Parpart
2005-04-20 15:35               ` Lance Albertson
2005-04-20 22:38             ` Donnie Berkholz
2005-04-16 13:18 ` [gentoo-dev] " Duncan
2005-04-20 16:39 ` [gentoo-dev] " Francesco Riosa

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=1113631832.10461.9.camel@mirage.ramereth.lan \
    --to=ramereth@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