Re: dependencies andapplications

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. 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! Maybe somebody of the pear-group could please summarize the ideas, call the public for a vote or do something else to get this thread to a definite way to go?!? Stefan