From: Peter Stuge <peter@stuge.se>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: News item: Apache "-D PHP5" needs update to "-D PHP"
Date: Mon, 4 Jan 2016 15:45:43 +0100 [thread overview]
Message-ID: <20160104144543.22864.qmail@stuge.se> (raw)
In-Reply-To: <568A73E8.6030304@gentoo.org>
Kristian Fiskerstrand wrote:
> Maybe I'm thinking things too difficult, why not just define both -D
> PHP and -D PHP5 in the transition period and suggest this config for
> any change?
Because it mostly just defers the problem.
If the desire is to move away from PHP5 then I would suggest to force
a failure when starting Apache, if PHP5 is defined when PHP is required.
Ie. fail closed.
I can be talked into supporting the idea to only print a warning when
PHP5 is set and to not fail (no source served) for some period of
time until which the forced failure starts, if PHP5 is still set.
Don't fail open, fail closed. Since manual interaction is required
some people will forget or overlook it, and will get a failure.
I would introduce the failure right away, but maybe a warning will
make some happy who would otherwise have gotten a failure.
//Peter
next prev parent reply other threads:[~2016-01-04 14:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 0:26 [gentoo-dev] News item: Apache "-D PHP5" needs update to "-D PHP" Sebastian Pipping
2016-01-04 5:11 ` Jeroen Roovers
2016-01-04 16:53 ` Michael Orlitzky
2016-01-04 8:41 ` [gentoo-dev] " Kristian Fiskerstrand
2016-01-04 12:11 ` Rich Freeman
2016-01-04 13:30 ` Kristian Fiskerstrand
2016-01-04 14:20 ` Kristian Fiskerstrand
2016-01-04 14:51 ` Rich Freeman
2016-01-04 14:45 ` Peter Stuge [this message]
2016-01-04 15:08 ` Brian Evans
2016-01-04 10:45 ` [gentoo-dev] " Lars Wendler
2016-01-04 13:40 ` Michał Górny
2016-01-04 15:20 ` Michael Orlitzky
2016-01-04 15:42 ` Peter Stuge
2016-01-04 15:53 ` Michael Orlitzky
2016-01-04 16:11 ` Peter Stuge
2016-01-04 16:43 ` Michael Orlitzky
2016-01-04 17:21 ` Brian Evans
2016-01-04 17:49 ` Rich Freeman
2016-01-04 19:27 ` Michael Orlitzky
2016-01-05 19:35 ` Michael Orlitzky
2016-01-06 19:36 ` Sebastian Pipping
2016-01-06 19:53 ` Michael Orlitzky
2016-01-08 0:52 ` Marc Schiffbauer
2016-01-09 17:39 ` Michael Orlitzky
2016-01-06 19:39 ` Sebastian Pipping
2016-01-04 15:11 ` Hanno Böck
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=20160104144543.22864.qmail@stuge.se \
--to=peter@stuge.se \
--cc=gentoo-dev@lists.gentoo.org \
/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