RE: [PEAR-DEV] (Fwd) [PEAR] RE: [PEAR-DEV] dependencies andapplications

On 21 Aug 2003 at 16:19, Lukas Smith wrote: > > From: Jan Schneider [mailto:jan@horde.org] > > Sent: Thursday, August 21, 2003 4:12 PM > > > Zitat von Jan Schneider <jan@horde.org>: > > > > > Zitat von Stefan Neufeind <stefan@neufeind.net>: > > > > > > > Why not keep the current directory structure for all packages that > > > already are released and switch to a new > > > Package/VersionNumber/Package.php > only > > > for > > > yet to be released packages or new major versions. > > > This would btw. also solve the problem with api changes in major > version > > upgrades. Old application will never see the new api because they > still > > use > > the old paths, we only have to take care that old major version > > don't > get > > uninstalled if the admin upgrades to a new major version. > > > > This should perhaps even be a general rule: only minor version > upgrades > > replace the old package (of course, because they are in the same > > directory), while major version upgrades leave the old version > installed. > > This way you can even release minor upgrades of all major versions > > independantely, e.g. you have 1.3 and 2.1 installed, and pear > > install-upgrades will update your packages to 1.4 and 2.3. > > And what about workarounds for bug fixes that you implement on your > application. Those could obviously lead to issues even on minor > version updates On minor updates those bug fixes shouldn't break BC. E.g. you are not allowed to change the API during a minor version update. So how should this "lead to issues"? For sure you can fix a bug and make it even worse ... but I think that's not what you were talking about :- )) Stefan