Re: Automated selection of engine

> I think in the long run it tends to be a bit ugly, but I don't see any > alternative right now, because merging the CVS histories doesn't seem to be > feasible to me. So I'm OK with it for now. With the empty branch concept, the unused engine directory contains only a single anti-pruning file. That would mean that the following branches need to emptied: ZE1: HEAD ZE2: PHP_4, PHP_4_3 > However, I am not convinced that having to explicitly checkout the PHP_5 > branch is such a good idea. I thought the idea was to have HEAD be the > current development version and branch if off when necessary. I would > prefer this kind of approach. That looks preferably to me as well. I've updated the instructions. http://schumann.cx/phpcvs.txt - Sascha