Edit report at https://pear.php.net/bugs/bug.php?id=17045&edit=1

  ID: 17045
  Updated by: daniel.oconnor@gmail.com
  Reported By: php at group dot apple dot com
  Summary: pearcmd.php ignores / overrides include_path
-Status: Open
+Status: Closed
  Type: Bug
  Package: PEAR
  Operating System: Mac OS X 10.6
  Package Version: 1.9.0
  PHP Version: 5.3.1
-Assigned To:
+Assigned To: glen
  Roadmap Versions:
  New Comment:

-Status: Open
+Status: Closed
-Assigned To:
+Assigned To: glen
This bug has been fixed in SVN.

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.

Previous Comments:

[2014-09-28 15:50:35] glen

Created PR for this https://github.com/pear/pear-core/pull/32


[2010-12-05 00:37:08] dufuz

Yeah, that may indeed be the way to go - I am going to investigate this
a bit more
and see if we have any knock on effects.

I am going to do the logging of the include_path but in a different way,
it may require
you to add a higher verbosity level on the logging (such as -vvvv) to
see that but at
least it will be in there in a more standardized way :-)


[2010-12-02 07:12:40] macphp

The logging was more for validating that the include_path is respected
development than to be left in for deployment. (With everything that
happens during a
full build, it was the only way I could see what the tool was using.)

And killing the include_path _prevents_ me (not allows me) to pass it on
command line since the required code can't be loaded in a bootstrap
Perhaps a check for INSTALL_ROOT or DESTDIR would treat the install as
raw or at
least skip the ini_set?


[2010-12-02 06:12:39] dufuz

I'm afraid that patch does not really solve the problem; The include
path setting is
there for a reason. I will have a look into if there is another way
around it or if we
get passed this somehow.
I do realise by killing of the include path setting it allows you to
pass in your own
include path on run time or it uses the one from the php.ini - Need to
the installation time.

Also, I am afraid we can not add any sort of logging like that which
goes out for
every single command a person runs. The reason being is that we have
switches which both dictate log levels and also the fact that certain
commands have
the ability to suppers any output (including error) but it wouldn't be
able to for this


[2010-12-02 05:58:40] macphp

I've attached a patch which disabled the call to ini_set() and adds a
helpful log message.


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 2 | next ›
Discussion Overview
grouppear-bugs @
postedOct 30, '14 at 3:20p
activeOct 30, '14 at 3:20p

1 user in discussion

Daniel Oconnor: 2 posts



site design / logo © 2022 Grokbase