Description: ------------ I'm working on 2 new commands: list-categories and list-category <category>. They are already in the webfrontend, but some more work is needed to put them in Command/Remote.php For release 1.6.0

have a patch yet?

Yip, its attached. Two add functionality to REST (1.0 and 1.1) The other one adds functionality to Remote.php The last one patches the Remote.xml file

Can't attach, too big. You can find the patches at: http://tias.ulyssis.org/patch/pear/listcategory

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. I've implemented the REST 1.1 functions. REST 1.1 is supported by all channel server code for over 1.5 years, we are not adding hacks to REST 1.0, just error out if the server does not support REST 1.1. Tias: adding new commands is the wrong way to implement this feature. The CLI frontend has absolutely no need for listing categories, you should access the REST directly for the web frontend. The same goes for the other attention on commands - "use the REST, Luke" Take a look at PEAR_Frontend_Gtk2 to see the best practices.

Hey, Thanks for including some of the code so far, some remarks: 1) REST1.0: There are still a few servers with REST1.0, like: components.ez.no and solarphp.com. Also, pearified.com has some invalid REST1.1 XML files, which means you have to fall back to REST1.0 if you want list-categories to work for it. I've done the effort of writing the code, I don't know if its such a big hassle to include it ? 2) The commands: I figured it would be a great addition to the PEAR CLI to have commands like 'list-categories': the current 'list-all' is very slow and returns waaaay to much data, having slicker commands like 'list-category' could solve this problem.

I've thought about this quite a bit before making a final decision. I will add the REST1.0 stuff As for the commands, my main concern is that the list of commands already scrolls off of the screen. I don't want to add any new commands at this point. PEAR 2.0 will have to fix this up somehow, perhaps with command categories.