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/

will implement after 1.4.0

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.

+1 to the approach :)