you mean that I can basically take PEAR and put it in a directory within Sinapse and just change the path of where PEAR is referenced in Sinapse files to the new directory I've just created
kinda... PEAR itself assumes all pear files are directly in the include path... so any calls with pear to other pear files is tricky to alter
your include_path is in your php.ini file
the only thing in my include path originally form my windows installation of php5 was '.'
so every call to include() or require() looked on in '.' or the current directory for the file, and didn't look anywhere else
after installing pear i changed it to
'.;C:\php5\pear'
so now include('PEAR.php'); will look first for '.\PEAR.php' and not find it. Then look in C:\php5\pear\PEAR.php and find it. you can add as many paths seperated by ; on windows or : on *nix/bsd systems
so if you don't have write access to your local php.ini file you can get around this by manually setting your include_path at the beginning of each script.. so subsequent calls to include() and require() can be made without thought to the local pear path.
Solution 1 )
put the include_path fudge in a file by itself... then have each file include that fudge file.
./pathfudge.php
<?php
set_include_path(get_include_path() . ":" . '/lib/pear/');
?>
./index.php
<?php
require_once('./pathfudge.php');
include('/HTML/QuickForm.php');
# etc....
?>
./admin/new/user.php
<?php
require_once('../../pathfudge.php');
include('/HTML/QuickForm.php');
# etc....
?>
you will have to make sure each and every file in your systems includes pathfudge.php at the correct depth
Solution 2 )
see if your webhost allows .htaccess files to be used. just plop a .htacess file in each directory setting whatever path you want
php_value include_path ".;C:/php5/pear/"
----
Punchline: Ask very nicely for your host to install the pear libraries you need, and adjust the include path to reflect pear.
