Re: Re: [RFC] PHP_Compat, MIME_Type & mime_content_type
| From: | Philippe Jausions | Date: | Mon, 27 Jun 2005 18:06:01 +0000 |
| Subject: | Re: Re: [RFC] PHP_Compat, MIME_Type & mime_content_type | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-38338@lists.php.net to get a copy of this message | ||
Justin Patrin wrote:
On 6/27/05, Joe Stump <joe@joestump.net> wrote:Most of the web sites on the internet are hosted by 3rd party companies and the web site owner doesn't have control over which PHP version is installed. Furthermore the hosting companies upgrade their PHP very slowly, which is a bad thing security-wise of course. But the point is that most web site owners will face that problem. This is why PHP_Compat was created in the first place. -PhilippeI'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".I'm not a package.xml expert so I can't answer the question, but the idea is ok. If package.xml does support this then we can allow this. I still don't really like it, though. This is why packages have PHP dependencies. You have to have a certain version to run it. If a user decides to use a lower version it's their responsibility to bring their installation up to a recent version of use PHP_Compat to *try* to bring it up.