Re: Third Party (Non-Official) PEAR Packages?
| From: | Alan Knowles | Date: | Thu, 07 Aug 2003 01:12:08 +0000 |
| Subject: | Re: Third Party (Non-Official) PEAR Packages? | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-19365@lists.php.net to get a copy of this message | ||
From what I remember the idea was to be able to add servers to the pear installer:
eg.
#pear list-servers
http://pear.php.net/xmlrpc.php
#pear add-server http://pear.horde.net/xmlrpc.php
#pear add-server http://phpclasses.org/xmlrpc.php
#pear add-server http://pearopen.sourceforge.net/xmlrpc.php
#pear remove-server http://pear.php.net
:)
So the pear installer will look through all servers to find packages..
This allows anyone to set up a pear distributing server (eg. like on sourceforge), where packages can go..
It's just a matter of someone having the time to dig though the installer to implement it...
Regards
Alan
Dmitri Vinogradov wrote:
"Thorsten Suckow-Homberg" <ts@siteartwork.de> schrieb im Newsbeitrag news:20030806232442.60387.qmail@pb1.pair.com...-- Can you help out? Need Consulting Services or Know of a Job? http://www.akbkhome.comI c, but how dow you want to avoid that functionality of third party-softwareisallready defined in some other (primary) package - or is gonna to be implemented as such afterwards?well... "There's more than one way to do it" (Larry Wall) ;) Don't think we must discuss the problem from this point of view - we couldn't avoid people use other solutions without waiting for upcoming PEAR releases as well ...I see a problem in keeping the balance - I think third party productsshouldbe added to the primary package as soon as there will be a need for the individual functionality this unofficial releases supply.Yes. and it's very good so. But we must think about one thing: PEAR was designed not just for PEAR-developers ;). You cant avoid people use PEAR infrastructure in their projects - PEAR is great, powerful and make live easier ;) I dont think PEAR stuff could ever become "another HotScripts-Project" - due to logic alone...Am I wrong if I fear that people won't use the primary packages (those for which PEAR was designed) - and instead keep downloading those unsupported packages?hm... Are we talking about concurent projects here? Dont think so... ;)Would PEAR become another "HotScripts"-Project?Regards DVRegards Thorsten