Re: [patch] BC breakage check

On 20 Sep 2003 at 2:22, Greg Beaver wrote: > 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. But again: You can't judge about all software running on your server if you're providing webhosting-services. There are not only package- deps (that could be resolved by the installer) but various tools from various places depending on various versions. On a private computer or if you only run software that you have developed yourself (maybe corporate server) this is no problem ... but please also consider the "large scale installations" where you don't know which scripts access which versions etc. Stefan