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

Bug #16423 Path to php binary should not be hardcoded
Submitted: 2009-07-10 08:13 UTC Modified: 2009-10-04 00:41 UTC
From: wrobel Assigned: kguest
Status: Closed Package: Date_Holidays (version 0.21.2)
PHP Version: 5.2.5 OS: Linux
Roadmaps: 0.21.5    
Subscription  


 [2009-07-10 08:13 UTC] wrobel (Gunnar Wrobel)
Description: ------------ Currently the two scripts offered by PEAR-Date_Holidays start with "#!/usr/bin/php". This needs to be fixed on platforms where this is not the patch to the php binary. Suggested patch attached.

Comments

 [2009-07-10 08:14 UTC] wrobel (Gunnar Wrobel)
The following patch has been added/updated: Patch Name: script_parser_path Revision: 1247213672 URL: http://pear.php.net/bugs/patch-display.php?bug=16423&patch=script_parser_path&revision=1247213672&display=1
 [2009-07-10 13:47 UTC] kguest (Ken Guest)
-Assigned To: +Assigned To: kguest
 [2009-07-27 15:43 UTC] cweiske (Christian Weiske)
Instead of hard-coding php_bin, use "/usr/bin/env php"
 [2009-07-27 18:11 UTC] wrobel (Gunnar Wrobel)
@Christian: I don't see how that would work for Windows or some platform where /usr/bin/env does not exist. @php_bin@ is not hard coded but a variable that is being replaced by the path to php as configured within PEAR.
 [2009-08-10 11:24 UTC] kguest (Ken Guest)
-Status: Assigned +Status: Closed
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/ fixed in release 0.21.4
 [2009-09-10 10:43 UTC] wrobel (Gunnar Wrobel)
-Status: Closed +Status: Open
This section of the patch on package.xml was not applied: + <file baseinstalldir="/" name="pear-dh-ini2xml" role="script"> + <replace from="@php_bin@" to="php_bin" type="pear-config"/> + </file>
 [2009-10-04 00:41 UTC] kguest (Ken Guest)
-Status: Assigned +Status: Closed
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.