Re: cvs: php4 /pear Makefile.in /pear/scripts .cvsignore pear-get.in pear.in

From: Date: Thu, 03 Jan 2002 07:44:12 +0000
Subject: Re: cvs: php4 /pear Makefile.in /pear/scripts .cvsignore pear-get.in pear.in
References: 1 2 3  Groups: php.pear.cvs 
Request: Send a blank email to pear-cvs+get-1803@lists.php.net to get a copy of this message
Jon Parise wrote: > > On Thu, Jan 03, 2002 at 12:24:11AM +0100, Stig S. Bakken wrote: > > > Of course. "pear-get" will be used for everything involving getting > > information or downloading from the web service: listing available > > packages/upgrades, displaying information, installing from the web etc. > > Of course, you can still install from local files with "pear-get > > install". > > > > The "pear" command is for the rest, especially package maintenance > > ("pear package" and so on). > > Why did you split off the "get" functionality from the "pear" > tool, though? Was it for performance reasons? It's easier to name the sub-commands then. What do you call the commands for: - listing packages on the server? list? list-remote? remote-list? list-remote-packages? - listing installed packages? list? list-installed? local-list? list-local-packages? etc. With "pear-get" you always work with the remote end, so it can be just "list" in both. I want to move the code for handling each sub-command out of the scripts though (into a subdir with one file per sub-command or something), so it's possible to reuse the code. - Stig

« previous php.pear.cvs (#1803) next »