Re: docs updated, working copy of php draft now available online
On Saturday 06 of August 2005 00:28, sean finney wrote:
> > 2 - pear (deb) packages restricted to one version of php, ex php5,
> > /usr/share/php/(VERSION)/pear
>
> this is what we're currently using, yes, though i've expressed an interest
> in phpPHPVERSION as an alternative. i think maybe this is something we
> can pass up the stream to the php maintainers for an opinion.
I agree that the solution should be backward compatible and consistent with
current php packages. So this is my last proposition:
INCLUDE_PATH:
/etc/php : for local administrator
/usr/local/share/php$MAJORVERSION : compatible with major version of PHP (i.e.
>= 5.0 or 4.0), locally installed
/usr/local/share/php : compatible with any version, locally installed
/usr/share/php$MAJORVERSION : compatible with major version
/usr/share/php : compatible with any version
/usr/share/pear : backward compatibility
EXTENSION_DIR:
/usr/local/lib/php$MAJORVERSION/$PHPAPI : locally installed
/usr/local/lib/php : locally installed
/usr/lib/php$MAJORVERSION/$PHPAPI : compatible with current major version of
PHP
PHPAPI=$(php-config --phpapi)
The question:
Should the web application set the include_path and extension_dir variables or
should rely on default settings? What if some administrator will overwrite
the default settings editing php.ini? The application should override them
again with .htaccess?
--
.''`. Piotr Roszatycki, Netia SA
: :' : mailto:Piotr_Roszatycki@netia.net.pl
`. `' mailto:dexter@debian.org
`-
Reply to: