Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21249 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47365 invoked by uid 1010); 16 Dec 2005 16:19:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 47350 invoked from network); 16 Dec 2005 16:19:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2005 16:19:38 -0000 X-Host-Fingerprint: 212.112.226.205 mail.nohn.net Linux 2.4/2.6 Received: from ([212.112.226.205:42309] helo=mail.nohn.net) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 19/13-14561-819E2A34 for ; Fri, 16 Dec 2005 11:19:37 -0500 Received: by mail.nohn.net (Postfix, from userid 1010) id 48B7E37C542; Fri, 16 Dec 2005 17:19:33 +0100 (CET) Received: from [192.168.2.101] (dslb-084-063-048-075.pools.arcor-ip.net [84.63.48.75]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.nohn.net (Postfix) with ESMTP id 72EF637C28D; Fri, 16 Dec 2005 17:19:22 +0100 (CET) Message-ID: <43A2E987.2030204@nohn.net> Date: Fri, 16 Dec 2005 17:21:27 +0100 User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ron Korving Cc: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on mail.nohn.net X-Spam-Status: No, hits=-104.9 required=5.0 tests=BAYES_00,USER_IN_WHITELIST autolearn=ham version=2.64 X-Spam-Level: Subject: Re: [PHP-DEV] RFE for future Apache integration From: sebastian@nohn.net (Sebastian Nohn) Ron Korving wrote: > I think it's very much worth fixing. More and more people use packaging > systems (emerge, dpkg, ...) which don't allow for what you propose. Not > everybody compiles their Apache and PHP themselves. It would be very > userfriendly if something like the solution suggested by techtonik would be > possible. You can use the same (packaged or not) Apache binary with different configurations and thus enable different modules for each instance you run. Sebastian