> > I'm not very concerned either way on the .ini extension > restriction. > > Let's go ahead and commit this with the "include" to > "additional_ini" name > > change. Perhaps the commit will stir up more feedback since there > has > > been so little. > > Some feedback: > > +1 for additional_ini=/path/to/new/additional.ini > -1 for including whole directories, since I think it has to great a > WTF factor.
Without scanning a directory, you would have to automatically edit and insert directives into files in order to add an extension automatically. It is so much easier just to drop a single ext.ini file in a dedicated ini dir and have it be read. Scanning a file and trying to figure out where to add stuff and making sure it isn't already there is a real PITA. Like the silly LoadModule stuff that apxs does. You often end up with multiple LoadModule lines for the same module. -Rasmus -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
