public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Varner <gentoo-dev@varnerfamily.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 07:38:55 -0500	[thread overview]
Message-ID: <1113655135.20336.3.camel@garath.homelinux.org> (raw)
In-Reply-To: <200504160656.43452@zippy.emcb.local>

On Sat, 2005-04-16 at 06:56 +0100, Elfyn McBratney wrote:
> 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)
> 

As a user whose apache install is completely hosed at the moment due to
these changes, my recommendation is all the above, with it being package
masked immediately.

Regards,
Paul
--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-04-16 12:38 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
2005-04-16 12:38 ` Paul Varner [this message]
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=1113655135.20336.3.camel@garath.homelinux.org \
    --to=gentoo-dev@varnerfamily.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