Re: Re: [RFC] PHP_Compat, MIME_Type & mime_content_type
| From: | Joe Stump | Date: | Mon, 27 Jun 2005 16:17:38 +0000 |
| Subject: | Re: Re: [RFC] PHP_Compat, MIME_Type & mime_content_type | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-38334@lists.php.net to get a copy of this message | ||
I'm confused. Can't authors simply require a specific version of PHP? I haven't looked over the package.xml specs in a while, but shouldn't I be able to say "If $version < 4.2, then require PHP_Compat"? I should at least be able to say "I see you like running old, buggy and potentially exploitable versions of PHP, in order to run this package or parts of this package you will need to install PHP_Compat".
--Joe
On Jun 27, 2005, at 9:18 AM, Helgi Þormar wrote:
On Mon, 2005-06-27 at 11:19 -0400, Philippe Jausions wrote:I don't remember seeing anywhere on the site how to deal with conditional dependency on PHP_Compat in a package. Let's say you want to use a fairly new useful PHP function such as str_split() (PHP 5) or file_get_contents() (PHP > 4.3.0). Should the package itself require_once the PHP/Compat/function/str_split.php or do you want to let that responsibility to the end user in their own script?What one should do IMHO is copy/paste from PHP_Compat and keep intact all respectful comments about who are the authors and where it was gotten from and such. - Helgi --PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php