Bug 173261 - "pear help uninstall" is incorrect
Summary: "pear help uninstall" is incorrect
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: php
Version: 4
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Joe Orton
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-11-15 18:53 UTC by Josh Kelley
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-11-15 16:17:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Josh Kelley 2005-11-15 18:53:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
"pear help uninstall" reports that -r (--register-only) is a valid command-line option, but that option is not implemented.

It would be nice if this option were implemented; it could make testing php-pear-* RPMs easier.


Version-Release number of selected component (if applicable):
php-pear-5.0.4-10.5

How reproducible:
Always

Steps to Reproduce:
1. Run "pear help uninstall" and note the documented -r option.
2. Run "pear uninstall -r XML_Parser"
  

Actual Results:  XML_Parser is unregistered and uninstalled.

Expected Results:  Ideally, XML_Parser is unregistered (no longer listed in "pear list") but its files are still present.

Less ideally, "pear help uninstall" would not list -r as an option, and "pear uninstall -r XML_Parser" would error out.

Additional info:

Comment 1 Tim Jackson 2005-12-31 12:03:19 UTC
I haven't tested with php-5.0.4, but with php-pear-1.4.5-5 this seems to be
fine. I just installed the DB package, then did:

pear uninstall --register-only DB

and now it is gone from "pear list", but:

# ls /usr/share/pear/DB*
/usr/share/pear/DB.php

/usr/share/pear/DB:
common.php  ibase.php  mssql.php   oci8.php   sqlite.php
dbase.php   ifx.php    mysqli.php  odbc.php   storage.php
fbsql.php   msql.php   mysql.php   pgsql.php  sybase.php

etc.

It's all still there.
If you are still experiencing problems, you may be better off pushing this
upstream to the PEAR guys.


Note You need to log in before you can comment on or make changes to this bug.