optional requirements

Hi, I just thought of having "optional dependencies" in PEAR packages. Example: A package provides a freaky caching feature that is used under special circumstances. For the normal package usage it is not necessary to have Cache installed, but in some rare cases it actually is. At such a point it would be good to have the possibility to mark a dependency optional: <deps> <dep type="pkg" rel="ge" version="1.0" optional>Cache</dep> </deps> During the package installation the user will be asked if he also wants to install the optional packages to make all features of the package available. If he does not chose to install them, the basic functions of the package will work as expected, but he may not be able to use some advanced stuff. Comments? - Martin -- Martin Jansen, <mail@martin-jansen.de> http://www.martin-jansen.de/