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 A431C1384B4 for ; Mon, 4 Jan 2016 19:26:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 207C521C002; Mon, 4 Jan 2016 19:26:37 +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 22EA5E0871 for ; Mon, 4 Jan 2016 19:26:36 +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 05ED8340871 for ; Mon, 4 Jan 2016 19:26:34 +0000 (UTC) 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> <568A8DA4.8000901@gentoo.org> <20160104154245.27599.qmail@stuge.se> <568A9592.5090401@gentoo.org> <20160104161153.30168.qmail@stuge.se> <568AA12D.7090807@gentoo.org> <568AAA13.8080006@gentoo.org> From: Michael Orlitzky X-Enigmail-Draft-Status: N1110 Message-ID: <568AC798.3040008@gentoo.org> Date: Mon, 4 Jan 2016 14:27:20 -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: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 9818c31a-e78a-4c3b-b99c-c4843019dd50 X-Archives-Hash: a81e489ce6844676d8645daa08fe47b0 On 01/04/2016 12:49 PM, Rich Freeman wrote: > > My understanding (which could be wrong) is that this update will break > things even if the user never runs eselect php afterwards. I can't > tell you the last time I touched the php eselect module, because major > updates to php are rare. > I was going to say "no, everything should keep working" but I decided to test a fresh upgrade before sticking my foot in my mouth. Now I know what people are complaining about. If you've never touched 70_mod_php5.conf, portage will remove it when you upgrade eselect-php. That does break an existing installation until you've run `eselect php...` and munged -DPHP5 to -DPHP. What I intended was for 70_mod_php5.conf to stick around until you've had a chance to deal with the configuration change. In that case everything keeps working until after you've run eselect. I may be able to fix that by simply including the old 70_mod_php5.conf for backwards compatibility.