Re: [PEPr] Comment on RFC::Drop requirement of renaming a package when migrating from PHP 4.x to PHP 5.x

On Sun, Jul 26, 2009 at 01:33:50PM +0100, Christian Weiske wrote: > PEAR's current version naming standard is in the manual: > http://pear.php.net/manual/en/rfc.version-naming.standard.php ... > This rule is not neccesary anymore when using Pyrus instead of the PEAR > installer, because Pyrus understands the api versions and errors out when > BC breaks occur, preventing the user from damaging his applications. So, > for PEAR1 packages, the rule should be followed. On PEAR2 packages, it is > to be dropped and ignored. Unfortunately, this still implies that all current PHP4-based, non-PEAR2 packages will still need to be renamed to migrate from PHP4 to PHP5 and/or PEAR2. -- Jon Parise (jon of php.net) :: The PHP Project (http://www.php.net/)