Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.9.4
Request #10390 Pyrus: provide a simple way to manage parent/child PEAR installations
Submitted: 2007-03-15 10:02 UTC Modified: 2011-06-24 17:48 UTC
From: cellog Assigned: mfonda
Status: Closed Package: PEAR (version CVS)
PHP Version: Irrelevant OS: n/a
Roadmaps: 2.0.0    
Subscription  


 [2007-03-15 10:02 UTC] cellog (Greg Beaver)
Description: ------------ When implementing cascading registries, it would be very important for breakage reasons to also allow a reverse cascade, so that the parent registry can determine whether an upgrade would break a child registry installation. This way, the child registries would not have to be protected from a bad upgrade by the parent registry.

Comments

 [2011-02-22 15:50 UTC] cweiske (Christian Weiske)
-Summary: provide a simple way to manage parent/child PEAR installations +Summary: Pyrus: provide a simple way to manage parent/child PEAR installations
 [2011-06-24 17:48 UTC] mfonda (Matthew Fonda)
-Status: Open +Status: Closed -Assigned To: +Assigned To: mfonda
This has been migrated over to the new Pyrus issue tracker on github: see https://github.com/pear2/PEAR2_Pyrus/issues/39