Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70382 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47923 invoked from network); 25 Nov 2013 16:39:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Nov 2013 16:39:30 -0000 Authentication-Results: pb1.pair.com header.from=rquadling@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=rquadling@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.177 as permitted sender) X-PHP-List-Original-Sender: rquadling@gmail.com X-Host-Fingerprint: 209.85.223.177 mail-ie0-f177.google.com Received: from [209.85.223.177] ([209.85.223.177:60559] helo=mail-ie0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 68/28-34377-14D73925 for ; Mon, 25 Nov 2013 11:39:29 -0500 Received: by mail-ie0-f177.google.com with SMTP id tp5so7059855ieb.8 for ; Mon, 25 Nov 2013 08:39:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=SO8L63c3OtfP+5GzcJlsoUqtX4wQvnaaHI60jbaQRBs=; b=mLPc5FmD/c9w9FLAddbX38Cmrbg5FWa2rAqJL3Cc5Z9+4t9qzWG1UYTCOP7/meUd85 HE3Wneopnt5N8DAz0dsg4IRCKD8o80jyynLnfcoUCOw4pzEUlo0QRTj3gWJvIuYvIA4z ltqyPeBX/U7ozerDbL8nTHkylMFQ2z/frGd+id2T02h56CX+Z0XEg8MzOFnn9SnuzKqm sXw6CrCci4FvF0IvICb8zF3av98Cn9ROV6mP2rVTw6NlTzIIfPlcBge4IBeEFDBSxUXi sJ/j0hdpO+WX52l2Xfys+MhXpfUrbI9arfdUCimCDwiHI2dalLiyRK+ofNsXOyJb1lTO OQIg== X-Received: by 10.50.27.104 with SMTP id s8mr13441507igg.4.1385397566148; Mon, 25 Nov 2013 08:39:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.223.10 with HTTP; Mon, 25 Nov 2013 08:39:06 -0800 (PST) Reply-To: RQuadling@GMail.com In-Reply-To: <1385395857.23451.76.camel@guybrush> References: <1385395857.23451.76.camel@guybrush> Date: Mon, 25 Nov 2013 16:39:06 +0000 Message-ID: To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= Cc: PHP internals Content-Type: multipart/alternative; boundary=047d7b10c9c3cd9a1d04ec0301e0 Subject: Re: [PHP-DEV] Allowing [SAPI=] entries in ini files. From: rquadling@gmail.com (Richard Quadling) --047d7b10c9c3cd9a1d04ec0301e0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 25 November 2013 16:10, Johannes Schl=C3=BCter = wrote: > On Sat, 2013-11-16 at 13:54 +0200, Richard Quadling wrote: > > I created a patch https://github.com/php/php-src/pull/466 to allow ini > > files to have a SAPI section, just like they can have a HOST and PATH > > section. > > Mind that we have per-SAPI configuration files (php-$SAPI.ini). > I'd like to keep the the number of ways to configure PHP limited in > order to prevent a mess ... > > In a per sapi ini file, the use of [SAPI=3D] for a non matching SAPI would have no effect (so at least it is safe to put them in). And just to repeat, the use of the additional directory for INI files precludes the use of sapi specific ini files, and this route is what I'm using to allow me the flexibility I need with our current hoster. Regards, Richard. --=20 Richard Quadling Twitter : @RQuadling --047d7b10c9c3cd9a1d04ec0301e0--