Description: ------------ > > What I'd like to see is a list of all files PEAR searches for > > configs, not only the files that were actually read. This would > > help with debugging. > I'm afraid but I have a doubt, Idon't really understand. Could you > explain me, perharps with a little example . PEAR looks for config files in - ~/.pearrc - /etc/pear.conf and sometimes in /usr/share/whatever/pear.conf or so When installing PEAR on cmdline as an own user, I get a pear config file in /home/myuser/.pearrc . The web server does not know anything about that user, so it does not use this config file because it looks for the config files somewhere else. The "somewhere else" is the information I am interested in, so that I can provide the pear config file on the correct location.

Christian, Is it possible that the information you look for is the one provided on top of CLI or Web result ouput PEAR => 1.7.2 Loaded Configuration File => C:\WINDOWS\pear.ini The "Loaded Configuration File" entry ? I'm not thinking to add a search function to find "user_file" (.pearrc) or "system_file" (pear.conf) on the full system files. It's too much : unless you've a good idea !

I don't want a "search potential files". The "loaded config files" is nearly what I want, but I would like to see a list of folders/files where PEAR *tried* to find a config file. Currently, PEAR_Info only lists the file(s) that actually exist and have been used. But when PEAR looks for a file in /home/$user/.pearrc and that file does not exist, it is not shown by PEAR_Info as a potential location of a config file.

Christian, I've finished my "draft" copy of what you hope to have in new version 1.9.0 of PEAR_Info. I hope to have cover all possible cases. Tell me if I've missed something. All links below go on a page with hightlighted source code used and 1 or more screenshots of given result I've given alternative configuration files a better render with help of CSS (default is to show file available in green and file not available in red). See all examples to see how its so easy to change the render. 1. Using default installation and default stylesheet http://www.laurent-laville.org/pear/pepr/PEAR_Info/requests/13741/pear_info.html 2. Using default installation and a custom stylesheet (blue skin) http://www.laurent-laville.org/pear/pepr/PEAR_Info/requests/13741/pear_info2.html 3. Using default installation and with template integration to a web page http://www.laurent-laville.org/pear/pepr/PEAR_Info/requests/13741/pear_info3.html 4. Custom installation with default stylesheet http://www.laurent-laville.org/pear/pepr/PEAR_Info/requests/13741/pear_info5.html 5. Another custom installation with default stylesheet http://www.laurent-laville.org/pear/pepr/PEAR_Info/requests/13741/pear_info7.html I'll commit the source code in PEAR CVS in next minutes: I've still to make change on CLI version Laurent

excellent

Thank you for your bug report. This issue has been fixed in the latest released version of the package, which you can download at http://pear.php.net/get/PEAR_Info