Re: dependencies andapplications

Zitat von Stefan Neufeind <stefan@neufeind.net>: > On 21 Aug 2003 at 17:05, Jan Schneider wrote: > > > Zitat von Lukas Smith <smith@backendmedia.com>: > > > > > The PEAR Installer for applications installs the pear packages that > > > are needed into a seperate directory. > > > > I still don't see a need for this. If one writes an application that > > depends on a certain version of a package, either the application is > > badly written or the package maintainer is so unreliable in keeping > > the api bc that you shouldn't use his package at all. I know you are starting to get confused ;-), but please don't mix up things. > In some cases you can't avoid breaking BC. Surely this has to be done > with a major version change (demanded by the pear-rules). But what if > you or a customer running on your server have an application > requiring the old API and one requiring the new one? With the > approach of being able to have multiple major versions installed at > the same time this problem is fixed for all time ... and I really > think it's the best solution to this - really! This case is handled with my approach. But Lukas talked about something different. Well, at least I think so, but maybe I'm confused now too. :-) He proposed that dependant packages that an application might have and that get installed by the pear installer, will be installed in a different directory only for that application. And that is a bad idea and unnecessary IMHO. If the packages' maintainers are not completly without a clue there is no need to not a rely on that applications won't break if you upgrade to a new minor version. Jan. -- http://www.horde.org - The Horde Project http://www.ammma.de - discover your knowledge http://www.tip4all.de - Deine private Tippgemeinschaft