[php-maint] Bug#674091: Bug#674091: php5: support configuration sets

Christoph Anton Mitterer calestyo at scientia.net
Wed May 23 18:58:14 UTC 2012

On Wed, 2012-05-23 at 12:21 +0200, Ondřej Surý wrote:
> /etc/php5/[SAPI]/conf.d is already used, so I don't really understand,
> what do you really propose? Have you checked the actual configuration
> before filling this bug?
Yeah I did.... but a) I missed the most important part of the report ^^
(see below) and b)...

You now introduced this mods-available dir,... which by itself is great,
but right right now /etc/php5/{SAPI}/conf.d is just a symlink
to /etc/php5/conf.d, right?
Nevertheless, AFAIU /etc/php5/{SAPI}/conf.d is intended to be the
"canonical" location... and it being a symlink to /etc/php5/conf.d is
just for convenience as they're for most users equal for each SAPI

Now you've added that php5enmod and php5dismod, but they seem to always
use /etc/php5/conf.d... so basically it breaks these assumptions.

> /etc/php5/[SAPI]/conf.d/ is really a symlink to ../conf.d/, but that
> can be easily changed by local administrator.
Is that going to be retained on upgrades?

> We will ship wheezy with just this enhancement (php5{en,dis}mod), and
> re-think if we can make the SAPIxEXT matrix easy enough to handle.
Ah :D

> P.S.: Ignoring the 'oh-PHP-is-so-insecure' rant...
Well that was not meant as rant,... just frustration by the recent
weeks ;)

The documentation in README.Debian documents everything already quite
nicely and you've added a good text for my notes about PHP_INI_SCAN_DIR.
a) Perhaps it's worth to add that /etc/php5/<SAPI>/php.ini itself is
still parsed, even if that is set.

(Now what I missed in the first place:)
b) The maxlifetime script obviously breaks if someone resets the
respective settings in a place that is not scanned, this seems to
include also the /etc/php5/{SAPI}/conf.d.

I guess making the script powerful enough to handle any custom locations
is probably difficult,... so perhaps another note would be good:
- that it doesn't look in non-standard locations
- what to do if different locations set different lifetimes

Ideally one could add some parameter or so, that allows some manual
setting of the the lifetime in e.g. /etc/default/php5 or so...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5677 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-php-maint/attachments/20120523/b5afa282/attachment.bin>

More information about the pkg-php-maint mailing list