Re: Installation
| From: | Stig Bakken | Date: | Tue, 29 Feb 2000 22:00:45 +0000 |
| Subject: | Re: Installation | ||
| References: | 1 2 3 4 | Groups: | php.pear |
| Request: | Send a blank email to php-pear+get-50@lists.php.net to get a copy of this message | ||
Damien Mc Kenna wrote:
>
> At 10:53 AM 2/29/00, you wrote:
> > Dependencies should first of all be between PEAR packages. Dependencies
> > to other things like special PHP versions or compile-time options, or
> > external programs, should IMHO be documented, but should not prevent you
> > from installing a PEAR package. Maybe a warning or something.
>
> In that case, what if you installed a package that eg required the
> mcrypt package but you didn't have it compiled in? Would it be up
> to the individual PEAR package to recognize it during runtime or
> should the installation fail? I'd vote for an installation fail.
I think the check should be runtime. What about having something like
this in the beginning of packages that require mcrypt:
<?php
if (!function_exists("mcrypt_create_iv")) {
if (!@dl("mcrypt.so")) {
// bail out
}
}
?>
- Stig