public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dylan Carlson <absinthe@gentoo.org>
To: Benjamin Podszun <ben@galactic-tales.de>, gentoo-dev@gentoo.org
Cc: "Thomas T. Veldhouse" <veldy@veldy.net>
Subject: Re: [gentoo-dev] dev-php/mod_php-4.3.1-r1 compile fails
Date: Fri, 14 Mar 2003 02:20:18 -0500	[thread overview]
Message-ID: <200303140220.18647.absinthe@gentoo.org> (raw)
In-Reply-To: <1047625298.5449.6.camel@localhost>

On Friday 14 March 2003 02:01 am, Benjamin Podszun wrote:
> Hi Tom.
>
> I think Apache2 should stay masked, since itwon't work with php yet. No
> idea what you use it for, but heavy load or using one of the newer mpms
> (PerChild for example) causes lots of segfaults.
> PHP and Apache2 are not production ready. That's what you should get
> when you ask both developer. Since LAMP is a common combination: Kep
> Apache2 masked.
> Btw: No idea what's ridiculous about this...

I disagree.

It's production ready enough for RedHat, SuSE.  We should be able to make 
it work.

Cheers,
Dylan Carlson

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
Key fingerprint = 3AEA DE38 FE42 15A6 C0E2 730E 3D04 BCC1 708E 165F

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-03-14  7:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13 18:31 [gentoo-dev] dev-php/mod_php-4.3.1-r1 compile fails Henti Smith
2003-03-13 18:35 ` Gertjan
2003-03-13 18:41   ` Henti Smith
2003-03-13 18:45     ` Gertjan
2003-03-13 18:54       ` Henti Smith
2003-03-13 18:55       ` Henti Smith
2003-03-14  0:12     ` Thomas T. Veldhouse
2003-03-14  7:01       ` Benjamin Podszun
2003-03-14  7:20         ` Dylan Carlson [this message]
2003-03-14  7:45           ` Thomas T. Veldhouse
2003-03-14  9:15             ` Benjamin Podszun
2003-03-14  9:31           ` Paul de Vrieze
2003-03-14  0:11   ` Thomas T. Veldhouse

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=200303140220.18647.absinthe@gentoo.org \
    --to=absinthe@gentoo.org \
    --cc=ben@galactic-tales.de \
    --cc=gentoo-dev@gentoo.org \
    --cc=veldy@veldy.net \
    /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