Edit report at http://pear.php.net/bugs/bug.php?id=10390&edit=1
ID: 10390
Updated by: [email protected]
Reported By: greg at chiaraquartet dot net
Summary: Pyrus: provide a simple way to manage parent/child
PEAR installations
-Status: Open
+Status: Closed
Type: Feature/Change Request
Package: PEAR
Operating System: n/a
Package Version: CVS
PHP Version: Irrelevant
-Assigned To:
+Assigned To: mfonda
Roadmap Versions:
New Comment:
-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
Previous Comments:
------------------------------------------------------------------------
[2011-02-22 15:50:40] cweiske
-Summary: provide a simple way to manage parent/child PEAR
installations
+Summary: Pyrus: provide a simple way to manage parent/child
PEAR installations
------------------------------------------------------------------------
[2007-03-15 10:02:43] cellog
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.
------------------------------------------------------------------------
--
Edit this bug report at http://pear.php.net/bugs/bug.php?id=10390&edit=1
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.