RE: [PEAR-DEV] Relativ Includes

> From: Mika Tuupola [mailto:tuupola@appelsiini.net] > Sent: Thursday, October 31, 2002 6:21 PM > To: Martin Jansen > Cc: Lukas Smith; 'Pierre-Alain Joye'; pear-dev@lists.php.net > Subject: Re: [PEAR-DEV] Relativ Includes > > 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? > my solution would force you to still have all your pear packages in one directory because otherwise you will run into issues with [require|include]_once() again because PEAR.php will be included multiple times etc. regards, Lukas