Re: BC breakage results

Zitat von Greg Beaver <greg@chiaraquartet.net>: > How's this for a solution: > > Add a requirement to the coding standards page that says if any other > PEAR packages depend on your package, and you are going to make a minor > change, you must notify the maintainer of that package so that they can > do a release that is compatible with your new package's version, or one > that requires an earlier version. A two week waiting period should be > allowed for people to respond, and then if nothing is heard back, it's > their problem and not yours if the minor break kills their package. I feel like fighting against wind mills. You just *don't know* who depends on your package. The world is bigger than the PEAR universe. And it's not acceptable that developers or users have to change/update their programs/packages because one package they depend on changes its api (and I think we're still talking about the api here) in version that should only contain bug fixes or enhancements. And your last sentence is simply arrogant. > As for the installer, I will code a new pear revert command that accepts > 1 argument: a package name, and has the -a --alldeps command. > > The revert command will simply restore a package to a previous install, > including any dependencies that must be downgraded (if a package has a > lt relation that is no longer satisfied) Sounds great. Jan. -- http://www.horde.org - The Horde Project http://www.ammma.de - discover your knowledge http://www.tip4all.de - Deine private Tippgemeinschaft