Re: Re: cvs: pear
/HTML_Progress/examples/monitordefault1.htmldefault1.phpdefault2.htmlfunction_callback.htmlfunction_callback.phphtmlpage.htmlhtmlpage.phpitdynamic.htmlitdynamic.phpmethod_callback.htmlmethod_callback.php
| From: | Greg Beaver | Date: | Tue, 26 Jul 2005 18:27:27 +0000 |
| Subject: | Re: Re: cvs: pear /HTML_Progress/examples/monitordefault1.htmldefault1.phpdefault2.htmlfunction_callback.htmlfunction_callback.phphtmlpage.htmlhtmlpage.phpitdynamic.htmlitdynamic.phpmethod_callback.htmlmethod_callback.php |
||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-38907@lists.php.net to get a copy of this message | ||
bertrand Gugger wrote:
Hi guys ! Again a bloody answer, Could not pear have a trigger: pear install --no-doc --no-test or pear install --only-necessaryhow about $ pear config-set doc_dir /dev/null :) I doubt this would actually work in PEAR 1.4, btw, it checks for creation of files. I don't think we need another command line switch for this. Those who really need to conserve disk space will be able to install on a local machine, strip the files and upload to the production server.
btw, I 'm still awaiting answers on: http://marc.theaimsgroup.com/?l=pear-dev&m=112020442805997&w=2I don't think such an "or" dependency is practical. It would triple the code size used for dependency validation and require a complex rewrite of DependencyDB, as well as breaking automatic dependency downloads. The best way to do this is to simply create a dependency group and do dependency validation in the code itself. Using this tag: <group name="compat" hint="PHP 4.3-5.1 users, install this group"> <package> <name>PHP_Compat</name> <min>1.4</min> </package> </group> Greg