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

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

On 1/17/07, David Sanders <dsandersbaselinesolutions.com.au> wrote:
> 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?
>

The only way to fix this right now would be to unserialize
the
registry and convert all paths to your new path. I'm not
sure if there
are current plans to fix this specific issue but Greg Beaver
has many
enhancements he is planning to make to PEAR regarding the
registry.

-- 
Justin Patrin

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Justin Patrin wrote:
> On 1/17/07, David Sanders <dsandersbaselinesolutions.com.au> wrote:
>> 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?
>>
> 
> The only way to fix this right now would be to
unserialize the
> registry and convert all paths to your new path. I'm
not sure if there
> are current plans to fix this specific issue but Greg
Beaver has many
> enhancements he is planning to make to PEAR regarding
the registry.

Hi,

The new PEAR registry for PEAR2 no longer stores absolute
paths.

Greg

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I was having the same problem last year. Unfortunately
there's no
*clean* solution right now besides what Justin said. See the
link to my
thread:

http://marc2.theaimsgroup.com/?l=pear-dev
&m=115322849900281&w=2

HTH,
- - Markus

David Sanders wrote:
> 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?
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFFtH0i1nS0RcInK9ARAlmdAKCzPlozOvn/EmT+hpE6XPxQ9KsV4QCg
ijgK
FzFxbGolyyt6rnmbqcT9dJ4=
=Ul6U
-----END PGP SIGNATURE-----

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php