From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 978811384B4 for ; Mon, 4 Jan 2016 15:19:26 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 08C3721C006; Mon, 4 Jan 2016 15:19:18 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1952CE086F for ; Mon, 4 Jan 2016 15:19:16 +0000 (UTC) Received: from [192.168.1.100] (c-98-218-46-55.hsd1.md.comcast.net [98.218.46.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mjo) by smtp.gentoo.org (Postfix) with ESMTPSA id EEC5D34076D for ; Mon, 4 Jan 2016 15:19:14 +0000 (UTC) From: Michael Orlitzky Subject: Re: [gentoo-dev] News item: Apache "-D PHP5" needs update to "-D PHP" To: gentoo-dev@lists.gentoo.org References: <5689BC34.5000006@gentoo.org> <20160104114537.392b9971@shanghai.paradoxon.rec> <20160104144036.1083a3d1.mgorny@gentoo.org> X-Enigmail-Draft-Status: N1110 Message-ID: <568A8DA4.8000901@gentoo.org> Date: Mon, 4 Jan 2016 10:20:04 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <20160104144036.1083a3d1.mgorny@gentoo.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: f87d88b5-d75a-4dd6-9280-1fe12481abb8 X-Archives-Hash: d9466197bb732e9e7ad44ba1c3f39058 On 01/04/2016 08:40 AM, Michał Górny wrote: > > Therefore, I think you should really work on some kind of backwards > compatibility for people using '-D PHP5' that would prevent those kind > of issues at least for some migration period. With big fat warnings for > people who run it. > I wasn't able to come up with something that worked on apache-2.2 and was backwards-compatible or failed "off." The apache module name for PHP changed with php-7.0. This forces a big change in 70_mod_php.conf, and a corresponding change in eselect-php (which must be run once before anything will work). The problem is to come up with an apache-2.2 config that works for new 5.6 users, 5.6 -> 7.0 eselect switchers, and new 7.0 users. Someone always gets screwed. If anyone has a concrete idea that works better, it's not too late to change it.