Re: Re: dependencies andapplications

From: Date: Thu, 21 Aug 2003 15:19:08 +0000
Subject: Re: Re: dependencies andapplications
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-20281@lists.php.net to get a copy of this message
On Thu, 21 Aug 2003 17:12:27 +0200 "Stefan Neufeind" <stefan@neufeind.net> wrote: > 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? Then you can install (and manage) 2 different PEAR trees as you already manage to web/whatever tree for your 2 applications. > 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?!? This kind of thing will not (and should not) be thought and approved in 1 or 2 days discussions on a ML. There are many things to check, valid, test before choosing one way or another (or drop the idea ;) ). pierre

« previous php.pear.dev (#20281) next »