Reindl Harald wrote:
Am 03.09.2011 17:19, schrieb Lester Caine:
> Adding a separate .ini for each package makes a lot more sense
this is usally done since years
> and all of the extension specific settings can be kept in the one place. You
can then load
> a database driver along with all it's own configuration simply by enabling
an .ini file?
tahts why --with-config-file-scan-dir exists
> And optional configurations are handled away from the core php.ini
fedora does this since i can think
Lots of distributions do this nicely, but not necessarily the same way?
My point was more that it would be nice if a clean stock install supported this,
and extensions managed their own ini files centrally, rather then each
distribution doing it's own thing? Some of the current discussions relate to
individual extensions, rather than core functionality so it would be nice simply
to wrap them in a way that they can be ignored if not applicable to a particular
installation?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
