Re: [Coding Standards] Loading all files at once
| From: | Joshua Eichorn | Date: | Fri, 13 Jul 2007 16:43:50 +0000 |
| Subject: | Re: [Coding Standards] Loading all files at once | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-47476@lists.php.net to get a copy of this message | ||
Travis Swicegood wrote:
Lukas Kahwe Smith wrote:-joshTravis Swicegood wrote:I could be completely mistaken. If it is the case to have one "package" that fits every need, there definitely will be issues with how to handle packaging as one size fits all is going to be harder to maintain. The first thing that comes to mind is any package that has code that needs to have replacements done via an installer task such as @php_bin@. -Travis You'd have to ask an installer guy to be sure but I think Greg's plan is to remove install time replacements and only do replacements at packaging time.Christian, I have to disagree with you here. The thing that keeps getting missed is that the unzip and go package is created by the package lead/developer. When I create it via 'pyrus package-zip' (or whatever), Pyrus will do all of the adjustments at that point, then that package can be distributed in a ready to use format. It's also worth noting that stray require_once calls are faster than doing an if(!class_exists()) check.I was not aware that the intention was to have a separate package for unzip and go people. I thought that the unzip and go would actually be an untar and go and we would work on having Pyrus do as much of any reorganizing and variable subtitutions as packaging time instead, so that people can take a PEAR package and untar or install.