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

PEAR's current version naming standard is in the manual: http://pear.php.net/manual/en/rfc.version-naming.standard.php It states that "The next major version is MyPackage2" - that's the issue we are facing here. The original reason for that rule is that the PEAR installer does not know when BC breaks occur. Package version does not sufficently express them, and the api version in the package is not used by the PEAR installer in any way. Thus, to prevent BC breaks through the normal upgrade process, it was decided to rename the package when doing a major overhaul like moving from PHP4 to PHP5, breaking BC. 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. -- http://pear.php.net/pepr/pepr-proposal-show.php?id=606