Re: [Coding Standards] Loading all files at once

Travis Swicegood wrote:

Joshua Eichorn wrote:

Travis 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@.

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.

Hopefully Greg will be able to weigh in soon and clear it up. Removing install time replacements is going to make creating packages like PHPUnit, PHP_Beautfier, etc., etc., next to impossible to distribute without people having to edit the scripts themselves or execute them via php -f scripts/phpunit. In nearly every CLI tool case, the latter is a bad option as PHP will gag when you try to add in your own arguments. -Travis My guess is that @php_bin@ will be the only install time replacement that is done. You won't be using @data_dir@ anymore (thats in the coding standard), and I think replacements for version etc will take place at packaging time.

But i haven't heard any talk about how @php_bin@ will be handled there might be something on the pear-core archives if someone is interested. -josh