RE: [PEAR-DEV] pear installer question.

> The difference between "pear" and "pear-get" is that "pear" does > local > operations, while pear-get does remote operations. I split them up to > make it easier to determine between commands like "pear-get list" (which > lists packages on the remote server), and "pear list" (which lists > packages you have installed). > > I'm still not entirely happy with the command structure. For example, > "uninstall" is a sub-command of "pear" now (because it is a local > operation), but this may not be obvious to everyone. Suggestions > welcome. :-) Eww! This sucks imho. The installer is, lets face it, for the common (l)user, and he/she most likely won't use it that much. This means that: o Ease of use is very important o The commands won't get memorised It would therefore be more userfriendly (imho I suppose) if it worked like so: o A single command, "pear" o Multiple descriptive operations, eg "list-installed", "install", "search" o Interactive nature for when the installer is not sure what to do, eg: [root@heyes_01 blaat]# pear install Mail_Mime Mail_Mime and Mail_mime-*.tgz not found! Would you like to try searching? [Y/n] y Searching... Found: 1 Mail_Mime-1.4.tgz 2 Mail_Mime-1.3.tgz 3 Mail_Mime-1.2.tgz 4 Mail_Mime-1.1.tgz 5 Mail_Mime-1.0.tgz Would you like to download and install any of these? [1-5/N] 3 Downloading Mail_Mime-1.2.tgz... Installing Mail_Mime-1.2.tgz... Finished! [root@heyes_01 blaat]# o If no operation is given or an invalid one, print a verbose usage! -- Richard Heyes