public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Evans <grknight@gentoo.org>
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 10:08:11 -0500	[thread overview]
Message-ID: <568A8ADB.70308@gentoo.org> (raw)
In-Reply-To: <568A3039.7070106@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 1/4/2016 3:41 AM, Kristian Fiskerstrand wrote:
> On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
>> Hi!
> 
> 
>> Better late then never.  Posting 72 hours from now the earliest
>> as advised by GLEP 42.  Feedback welcome as usual.
> 
> Do you have any timeline in place for the change happening in tree
> (in particular for stable users).
> 
> 
>> Without updating APACHE2_OPTS, websites could end up serving PHP
>>  code (include configuration files with passwords) unprocessed to
>>  website visitors!
> 
> 
> Such a change should really be avoided if possible. Would it be 
> possible to have a conditional approach where either one can be
> used, or maybe set the new variable/defin if the old one is used?
> 
> 

The problem is really two-fold with the new eselect-php.

For future compatibility (to not have this happen again with say
PHP8), the PHP team changed the symlink created by eselect to be
libphp.so instead of the current libphp${MAJOR}.so.

The user must also reselect with `eselect php set X`, even for the
current PHP versions and not just 7.

mjo explored the option of "<IfDefine PHP5>Define PHP</IfDefine>" but
that is apache-2.4+ only.

If we wanted a "compatibility" layer, it would be the same section
repeated until 2.4 was the only version available.  That might confuse
users even more.

Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)

iQIcBAEBAgAGBQJWioraAAoJENH3ge/59KO2wNUQAKThJz1QBjOvOmi0ClluVxt8
Lt0fbibQXIgZScJy5zqeOwX3EAUDqBST8sonNhJ8uQT4qbU8gwdYK6vhoDbJS0sX
oNzbdwxumSwNBsi4UCl/D0Dj+XefgIyvmgGBZ0RA8t0x8Ls3uQB6DWI1f36Z3wAs
ULqJc38+d1e5pmNu3jpc5tvG2ybvaVVGbWmNiOI8rafFV12KIsRMDHdDCG4DpkQD
bmWLYTv44Nt5nSY2wmLQQAV57kB2PsaaT0qlQciVhKiqOUA+qlmI0dtM3LLSNitK
dqKWNj7WTQFBM1SLHXD0s4CQk9XhFB9E07zelcB5zuC9XeYj1mbrn9aEtfl5lfVs
hHHJQ97MG3u/XwPTHY04J6wfoaQW4dwaQd74Pz48qJ2DqSW9HV8UTS2enF5cuZok
mFfd+xexHvcz45jyz83BtXM4mRWdHBDdy/3fYEvN12wVgU4hQcjDTKKPwpO3Btsb
uyCar+SgoHoRIEQhfDytnT0Idte2GifCysPq7hG12j+efwT7pt0XXk+TZQaH/opZ
FWRzOvjXZXd41M3RQ7H5D+KXrKV3uY4mE41rceEUXrw9PQrueg6Cw5ujK/opawrv
a8qonCtx7LZrEzYLagCYEBDPdgvxHWzIBb0vdgYoRVzSRwoJiAA66dbRuqC7s34G
JM84VqrtPsaCktCq6vw3
=/gh0
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2016-01-04 15:07 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
2016-01-04 15:08   ` Brian Evans [this message]
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=568A8ADB.70308@gentoo.org \
    --to=grknight@gentoo.org \
    --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