CLI Problems
| From: | Timothy Marsolais | Date: | Mon, 09 Jan 2006 22:17:22 +0000 |
| Subject: | CLI Problems | ||
| Groups: | php.pear.general | ||
| Request: | Send a blank email to pear-general+get-22480@lists.php.net to get a copy of this message | ||
Hi,
I have incorporated PEAR into every project I can, and have run into a whole
host of problems since the security problem was discovered in November. Prior
to then, I had been using the Web interface and installing a local copy on a
shared host. After the security vulnerability was fixed, my 20 PEAR projects
have been stranded.
I have been able to request shell access from the hoster, but with the CLI I
have yet found a successful configuration. I get an error message saying that
I cannot install a local copy of pear without a previously existing copy of
PEAR. The hoster is running an older version of PEAR, but I cannot update the
packages because it is a system-wide installation of PEAR bundled with PHP--and
I do not, nor will I, have access to the that portion of the server.
I can install packages, list, delete, etc. All of the PEAR CLI commands work
fine, excepting that I cannot install anything that requires PEAR as a
dependency. So, Mail is fine, but DB is out of the question--as well as the
updated version of PEAR. It requires a previous version of PEAR.
Is there a way to set the pear config file to use the system version of PEAR as
the base so I can install a complete and current version of PEAR locally for
each project?
If this is a developer's list question, please let me know. I joined that list,
as well.
I hate the thought of NOT using PEAR in my projects--using my old code to
replace PEAR seems like such a digression . . . . Thanks, in advance for any
help.
-Tim
---------------------------------------
* Timothy Marsolais *
* http://www.Technology-Works.Net *
* 916.996.6542 *
* Build Projects that Matter *
---------------------------------------