Problems upgrading pear packages with a copied pear repository

Hi all, I create an instance of a pear repository for each web application that I create. I also add this pear repository to svn. Sometimes I'll check out an application into a different workspace and try to update the pear repository from this new workspace. I've always thought that just switching php_dir, doc_dir, data_dir and test_dir over to the new location would take care of this and this works just fine for installing new packages. However I've just found out that the .registry stores the full absolute pathname of the installed package that it was first installed into. Then when I try to upgrade certain packages, pear tries to delete the packages from the original location. Is there any way around this problem? I would've thought that the best way to handle this would be to only store the relative pathname from the pear root, and prefix the php_dir setting onto the front when attempting to delete files? -- David Sanders