Re: Relativ Includes
| From: | Mika Tuupola | Date: | Thu, 31 Oct 2002 17:20:59 +0000 |
| Subject: | Re: Relativ Includes | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-10386@lists.php.net to get a copy of this message | ||
On Thu, 31 Oct 2002, Martin Jansen wrote:
> Imagine one wants to upgrade to a newer version of package XYZ. This
> newer version of XYZ makes use of PEAR_INCLUDEPATH but the user does
> run a version of PEAR that does not set the constant. So he will
> possibly run into trouble when upgrading to the new package, because
> he also has to upgrade to a recent PEAR version then.
And if all libraries honor PEAR_INCLUDE_PATH I can not see
what is the difference with:
ini_set('include_path', '/foo/');
since all the libraries would use newly introduced
PEAR_INCLUDE_PATH.
Wouldn't per directory ini_set() via .htaccess be more of
the solution if you want some of the code to have a
different include_path that the default one?
--
Mika Tuupola http://www.appelsiini.net/~tuupola/