Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.10.15

Bug #12001 could not overwrite download_dir from environment variable?
Submitted: 2007-09-07 07:45 UTC
From: hio Assigned: hio
Status: Closed Package: PEAR (version 1.6.1)
PHP Version: 5.2.4 OS: Linux
Roadmaps: 1.6.2    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 32 + 35 = ?

 
 [2007-09-07 07:45 UTC] hio (Yamashina Hio)
Description: ------------ PEAR_CONFIG_DEFAULT_DOWNLOAD_DIR is defined. But default value for download_dir is set as PEAR_CONFIG_DEFAULT_CACHE_DIR and PEAR_CONFIG_DEFAULT_DOWNLOAD_DIR is not used at anywhere. 'download_dir' => array( 'type' => 'directory', 'default' => PEAR_CONFIG_DEFAULT_CACHE_DIR, 'doc' => 'directory which is used for all downloaded files', 'prompt' => 'PEAR Installer download directory', 'group' => 'File Locations (Advanced)', ), Test script: --------------- $ PHP_PEAR_CACHE_DIR=cache PHP_PEAR_DOWNLOAD_DIR=download pear config-show | grep 'cache\|download' PEAR Installer cache directory cache_dir cache PEAR Installer download download_dir cache Cache TimeToLive cache_ttl 3600 Expected result: ---------------- $ PHP_PEAR_CACHE_DIR=cache PHP_PEAR_DOWNLOAD_DIR=download pear config-show | grep 'cache\|download' PEAR Installer cache directory cache_dir cache PEAR Installer download download_dir download Actual result: -------------- $ PHP_PEAR_CACHE_DIR=cache PHP_PEAR_DOWNLOAD_DIR=download pear config-show | grep 'cache\|download' PEAR Installer cache directory cache_dir cache PEAR Installer download download_dir download

Comments

 [2007-09-08 15:08 UTC] cellog (Greg Beaver)
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.