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

The current PEAR requirement to suffix a package name with "2" is not limited to packages changing from PHP4 to PHP5. The current rule applies any time a BC break is made to a stable package. I'm not sure this rule will ever be able to be lifted for stable packages. The problem is sometimes you need to have both the old version and new version of the API installed and used in one application. For example, the Services_Amazon_S3 package dependeds on HTTP_Request2 while Services_oAuth depends on HTTP_Request. If this proposal were accepted, it would not be possible to use S3 and oAuth from PEAR in the same application. There was a PEAR RFC drafted for this proposal which I am not currently in favor of approving for this reason: http://wiki.php.net/pear/rfc/pear2_versioning_standard_revision This thread on PEAR-dev details my concerns: http://thread.gmane.org/gmane.comp.php.pear.devel/47696/focus=48629 Also note the current rule does NOT apply to unstable packages. If there is a PHP4 compatible package in PEAR that is not marked as stable, it can be moved to PHP5-only code without changing the package name. -- http://pear.php.net/pepr/pepr-proposal-show.php?id=606