Pyrus status: nearly ready for release (was Re: [PEAR-DEV] 2009 Elections! Are YOU ready? | state of pear)

David Coallier wrote: > - Get PEAR2 going (This includes getting tests written for Pyrus) Hi, As an FYI, Pyrus's test coverage currently stands at 76% (the PEAR Installer, by contrast, is at about 62%). Pyrus is not yet feature complete, but supports and is unit tested fully on several use cases that PEAR does not support: 1) manage an existing PEAR installation seamlessly with pyrus (PEAR supports this, obviously :) 2) repair a corrupted installation (redundant registries) 3) automatically detect PEAR installations in include_path and use them for both listing packages and satisfying dependencies 4) unzip a PEAR2 package, then upgrade it immediately with "pyrus /path/to/package PackageName" (no installation necessary even for upgrade). This only works with PEAR2. PEAR packages still have to be installed before Pyrus will see them. 5) bundle a package inside an application, and use pyrus to upgrade it and dependencies, a minimum number of files are kept around (just the package.xml and channel.xml) 6) manage multiple PEAR installations without any potential for confusion of configurations 7) full support for packages in .tgz/.tbz/.tar/.zip/.phar out of the box 8) upgrade existing PEAR to newer, more robust registries 9) easy, instant creation of package.xml from a directory layout (i.e. PEAR_PackageFileManager now is part of the core, and is much simpler), and simple package creation. (this is not yet unit tested, but seems to work great) 10) simple channel creation and maintenance directly from package release files. (this is not yet unit tested, but seems to work great) Things PEAR does that are not yet implemented: 1) download progress bar (AHEM PEAR2_HTTP_Request maintainers) 2) post-install scripts (this is next on my list, probably today or early tomorrow) 3) custom plugins (custom roles/tasks/scripts) (will be handled along with #2, and is partially implemented) 4) web frontend 5) cli frontend isn't quite advanced enough yet (options/help and such) 6) gtk frontend 7) "info" and "remote-*" commands, list-upgrades etc. Thanks, Greg