Edit report at https://pear.php.net/bugs/bug.php?id=4208&edit=1
ID: 4208
Updated by: [email protected]
Reported By: cellog at php dot net
Summary: Add ability to migrate a package to another channel
Status: Open
Type: Feature/Change Request
Package: PEAR
Operating System: n/a
PHP Version: Irrelevant
Roadmap Versions:
New Comment:
+1 to the approach :)
Previous Comments:
------------------------------------------------------------------------
[2009-03-27 00:05:00] dufuz
Had a back and forth with people about this and most people wanted a
prompt (something not possible in the PEAR installer, per se) so what I
came up with (no patch yet) is if we would do this on phpunit then I
would install the package, get up a msg saying "this package has moved,
run pear upgrade -m phpunit" and it would auto discover the new channel
and install that package instead of the old one, effectively migrate the
package over.
So this would entitle upgrade to get a new switch option -m or
--migrate. This is the closest we can get to a prompt without being an
actual prompt.
Any thoughts on the approach.
------------------------------------------------------------------------
[2005-05-11 22:58:53] cellog
will implement after 1.4.0
------------------------------------------------------------------------
[2005-04-22 19:42:05] cellog
Description:
------------
Currently, once a package is in a channel, it is stuck. This means if
you ever move it to another channel, you have to use --ignore-errors to
install it because it will conflict with the package from the other
channel.
Security is an issue, so the only way to do this is to have the
specification in the old channel's final release, as in:
<name>Chiara_PEAR_Server</name>
<channel>pear.chiaraquartet.net</channel>
<deprecatedby>
<name>PEAR_Server</name>
<channel>pear.php.net</channel>
</deprecatedby>
This would be the top of Chiara_PEAR_Server's final release at
pear.chiaraquartet.net. The releases at pear.php.net would then be able
to upgrade from the older Chiara_PEAR_Server with no penalty.
This is most useful for a package that retains the same name. The
example above is moot, because a Chiara_PEAR_Server package would not
conflict with a PEAR_Server because all the files are in Chiara/
------------------------------------------------------------------------
