(Fwd) [PEAR] RE: [PEAR-DEV] dependencies and applications

Sorry, was supposed to go to pear-dev actually ... ------- Forwarded message follows ------- From: "Stefan Neufeind" <stefan@neufeind.net> To: pear-general@lists.php.net Date sent: Thu, 21 Aug 2003 15:20:36 +0200 Copies to: "Lukas Smith" <smith@backendmedia.com>, "Greg Beaver" <greg@chiaraquartet.net> Priority: normal Subject: [PEAR] RE: [PEAR-DEV] dependencies and applications [ Double-click this line for list subscription options ] On 21 Aug 2003 at 9:30, Lukas Smith wrote: > > From: Greg Beaver [mailto:greg@chiaraquartet.net] > > Sent: Wednesday, August 20, 2003 11:17 PM > > [...] > > This could be solved by distinguishing between extensions and > > applications. PEAR is designed strictly for extensions now (PER > > as Harry stated). Applications need to be handled separately, and > > I > would > > suggest that all applications would need their own local copy of > global > > packages. > > Yes these are the limits of the PEAR installer atm. > I personally bundle all PEAR packages with my applications. This > seems to be the only way to really be sure things are working right. > All the solutions mentioned in this thread are not ideal. However if > you have an installer handle the updating of packages for the > applications the main issue seems to be disk usage, which I find the > smallest issue to accept. Well, I personally rate a central pear-installation quite useful / necessary. And in my eyes we should follow the idea that there might an MDB-version from the 1.x-tree and one from the 2.x-tree. If you ship every package with every app you can't even centralize updates to the 2.x-tree or something. And caching (php-accelerator etc.) would also require separate caching per application. Hmm - I'm in favour of a centralized solution through pear itself. As mentioned earlier (but to put it a bit different): Maybe having pear/MDB/MDB.php for all 1.x-releases and from PEAR 1.3 on also have pear/MDB/1.0/MDB.php is fine. From PEAR 2.0 on we can issue the warning as outlined before it still pear/MDB/MDB.php is used. And from 2.5 or so we should finally abandone these warning- files as well. From 1.3 to 2.0 there would be enough time for every package and every programmer out there to update his programs to work without any warnings. And when 2.0 comes out there is still some time until 2.5 finally breaks BC completely. What's so bad about such a solution? Stefan -- PEAR General Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php ------- End of forwarded message -------