Report new bug | New search | Development Roadmap Status: Open | Feedback | All

Bug #7524 Inadequate instructions
Submitted: 2006-04-30 04:21 UTC
From: edgar_ware at yahoo dot com dot au Assigned:
Status: No Feedback Package: Documentation
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
Subscription  
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes. If this is not your bug, you can add a comment by following this link. If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
2006-09-23 09:49 UTC
Package:
Bug Type:
Summary:
From: edgar_ware at yahoo dot com dot au
New email:
PHP Version: Package Version: OS:

 

 [2006-04-30 04:21 UTC] edgar_ware at yahoo dot com dot au (Edgar Anderson)
Description: ------------ I've been attempting to set up an instance of PEAR using the instructions at http://pear.php.net/manual/en/installation.shared.php and I am finding them to be less than less than adequate for the task. My experience working with linux/unix is limited and rudimentary, and as the instructions at the aforementioned URL expect you to have far more knowledge than they should, they have bamboozled me several times. Firstly, the line "if you add ~/pear/bin to your path as the first entry in .bashrc (or whatever your startup file is)" makes no sense, and consequently as I cannot perform this step of the setup. The command "pear install -o PEAR" which you are asked to perform next does not succeed. I did not even bother attempting the "Installing a local copy of PEAR through ftp/ftps/sftp" method - if I can't get this to work using a method which requires only three steps, I'm not even going to bother with a method which requires fifty. If I thought that there were too many assumptions made in the "Installing a local copy of PEAR through SSH" section, GOD HELP anyone who tries to use the go-pear script. The standard of the documentation in PEAR and it's associated packages is unbelievably bad at the best of times. Too many times I have found myself poring over uncommented source code in a vain attempt to discover aspects of a pakage's functionality. I strongly suggest making some inroads into improving it as the poor standard of documentation which is generally assocuated with open source software unfairly taints the underlying programs which, once you wade through the unnecessarily compicated process of discovering how to use them, are generally very good.

Comments

 [2006-04-30 11:21 UTC] User who submitted this comment has not confirmed identity
If you submitted this note, check your email.If you do not have a message, click here to re-send
MANUAL CONFIRMATION IS NOT POSSIBLE.  Write a message to pear-dev@lists.php.net
to request the confirmation link.  All bugs/comments/patches associated with this

email address will be deleted within 48 hours if the account request is not confirmed!
 [2006-09-23 09:49 UTC] User who submitted this comment has not confirmed identity
If you submitted this note, check your email.If you do not have a message, click here to re-send
MANUAL CONFIRMATION IS NOT POSSIBLE.  Write a message to pear-dev@lists.php.net
to request the confirmation link.  All bugs/comments/patches associated with this

email address will be deleted within 48 hours if the account request is not confirmed!