Description: ------------ I tried to install a second copy of pear on my server since my user needs to install package himself. I followed http://pear.php.net/manual/en/installation.shared.php . After config-create I tried $ pear install -o PEAR and got > Could not download from "http://pear.php.net/get/PEAR- > 1.5.4.tgz", cannot download "pear/PEAR" (could not open / > tmp/pear/cache/PEAR-1.5.4.tgz for writing) Ok, no problem - set your own temp dir. $ pear config-get temp_dir && pear install -o PEAR /tmp/pearscu/ Did not download optional dependencies: pear/XML_RPC, use --alldeps to download automatically pear/PEAR can optionally use package "pear/XML_RPC" (version >= 1.4.0) downloading PEAR-1.5.4.tgz ... Could not download from "http://pear.php.net/get/PEAR-1.5.4.tgz", cannot download "pear/PEAR" (could not open /tmp/pear/cache/PEAR-1.5.4.tgz for writing) It seems that the temp_dir setting is not respected when installing packages.

cache_dir is not respected, I don't know about temp_dir. $ pear config-get cache_dir /home/scriptuser/pear/pear/cache

download_dir is used for downloads, so you need to set download_dir. cache_dir is only used for REST/XMLRPC caching Perhaps a better error message would help.

It works when I change download_dir.

Is there a separate problem here that config-create doesn't set download_dir?

timj: yes, that appears to be an issue on several machines I've tested

Is it supposed to set it? It certainly doesn't on Fedora/Red Hat but I've never got round to investigating whether it's: a) PEAR not even trying to set it b) PEAR trying to set it but not doing it due to a bug c) a Fedora packaging bug

I think it should set it. You see the problems arising when not setting it.

I agree 100%. Same for temp_dir. Which is why we need to figure out which of (a), (b), or (c) in my last comment is true :)

PEAR/Command/Config.php#351: It does not try to set download_dir.

OK, bug #11251 opened (this issue remains about the fact that errors related to download_dir are not clearly reported)

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.