public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stuart Herbert" <stuart@myrddraal.demon.co.uk>
To: "'Donny Davies'" <woodchip@gentoo.org>, <gentoo-core@gentoo.org>
Cc: <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] HEADS UP: Twitching to un-arch-mask Apache2
Date: Mon, 23 Jun 2003 12:11:37 +0100	[thread overview]
Message-ID: <000001c33978$48bd2540$c500a8c0@Churchill> (raw)
In-Reply-To: <20030622214532.GA25405@breccia.escarpment>

Hi Donny,

>   The time has come (slightly overdue) to make Apache2 the 
> default version on Gentoo.  Because it is still ~arch masked, 
> you only get it "by default" if you run the "unstable" 
> flavour around here.

PHP is still not recommended for production use with Apache 2
(http://www.php.net/manual/en/install.apache2.php).

That said, PHP 4.3.2-r2 runs fine for me under Apache 2 on Gentoo (so far).

>   I'm sure most of you know that distros like RedHat and 
> Mandrake (plus undoubtedly several others) give you this 
> version by default, and provide Apache1 packages for those 
> who still want it.

Good for them ;-)  

RedHat and Mandrake have already "migrated" to rpm.  Does that mean Gentoo
will be too in the near future?
Sarcasm aside, is "keeping up with the Jones's" really that important?

>   Help us to understand where we are and where we're going 
> with this.  We're a little behind on this upgrade, so let's 
> get moving.

I'm sure I'm not the only person who has no plans to migrate away from a
working (and very stable!) Apache 1.3.x solution in the near future.  I have
production servers running on this stuff, and being able to still use Apache
1 on Gentoo is important to my business.  Apache 1 & 2 installing into
separate slots is great news (why doesn't 'USE="-apache2 apache" emerge -p
apache' offer to install Apache 1 tho?  It offers to rebuild Apache 2
only.).  But already I'm coming across (unstable) ebuilds that have been
written to only install with Apache 2 (even tho they're building software
that works with Apache 1 as well).

Is there going to be some sort of "policy decision" on whether new ebuilds
should still support Apache 1 as well (where possible, of course), and for
how long?  And, yes, I'm willing to volunteer to help maintain support for
Apache 1 in other ebuilds if that's what it takes.

Best regards,
Stu
--



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-23 11:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 21:45 [gentoo-dev] HEADS UP: Twitching to un-arch-mask Apache2 Donny Davies
2003-06-23 11:11 ` Stuart Herbert [this message]
2003-06-23 12:34   ` Chris Bainbridge
2003-06-23 12:22     ` Stuart Herbert
2003-06-23 13:22       ` Chris Bainbridge
2003-06-23 17:16     ` Jon Portnoy
2003-06-23 13:56   ` Brian Jackson
2003-06-23 16:36   ` Robin H.Johnson
2003-06-23 15:16 ` Dhruba Bandopadhyay
2003-06-23 22:46   ` William Kenworthy
2003-06-24  2:22     ` Robin H.Johnson
2003-06-24  7:41       ` Paul de Vrieze
2003-06-29 21:53 ` Aron Griffis
2003-06-29 23:20   ` Donny Davies
2003-06-30 16:03     ` Kumba

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='000001c33978$48bd2540$c500a8c0@Churchill' \
    --to=stuart@myrddraal.demon.co.uk \
    --cc=gentoo-core@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=woodchip@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