PEAR Development Environment

Hello fruit people, I am developing a package and usage of the package at the same time. Currently, I have to repackage and pear upgrade using the .tgz release. This forces me to update some version numbers and stuff that I should be doing, but I can't really do it all the time while I'm making very minor adjustments. Is there a simple way (besides individual require_once hacks and ini_set) to set up a development PEAR environment ? I guess I could create a link to /usr/share/php/Services/ for my Services_Shipping stuff. Also, my SVN structure is slightly different than my package.xml structure. I keep things inside their directories. For example, in the PEAR package XML.php is in Services/Shipping, but the SVN it's actually in Services/Shipping/XML. Is this okay, or not good for you guys? This also promotes an issue with making a simple solution like a symlink, as mentioned before. Cheers, Kristopher Ives Santiance Corporation