[patch] BC breakage check
| From: | Greg Beaver | Date: | Sat, 20 Sep 2003 06:22:11 +0000 |
| Subject: | [patch] BC breakage check | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-21820@lists.php.net to get a copy of this message | ||
Hi all,
I've coded the first step in BC enforcement. The attached patch made against current PEAR CVS does a couple of things:
- It adds saving of major version number as a part of the registry so that <replace type="package-info" from="@API-VER@" to="majorversion" /> will allow the apiVersion() method to always return the major version installed, without programmer brain needed. you would code this method:
function apiVersion()
{
return '@API-VER@';} - It adds a check on upgrade to make sure that the major version has not increased, and fails if so - If passed --force, it will install anyways with only a warning. These changes mean that users must consider the consequences of upgrading to a major version. I'm only posting the patch here because I want to make sure it looks spectacular to everyone, before committing it, not just PEAR core folks. :) Greg