Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:2677
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Tue, 24 Jun 2003 05:25:54 +0200 (CEST)
To: internals@lists.php.net
Message-ID: <Pine.LNX.4.53.0306240509480.32741@eco.foo>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Automated selection of engine
From: sascha@schumann.cx (Sascha Schumann)

    Right now, CVS users have to know which engine they need for
    a particular PHP version.  The reason for this?  The
    php4/php5 CVS aliases have been removed, because they
    conveyed a false impression -- php4 just wouldn't give you
    PHP 4, if you did not also specify the correct branch.

    So we are better off just relying on the branch info instead
    of pretending that a CVS alias might do the trick.

    Thus, how do we make

        cvs co -r PHP_4 php-src
        cvs co -r PHP_5 php-src

    just work?

    The simplest solution seems to be: Check out both engines all
    the time.

    This is simple on the CVS level, but there are two other
    concerns:

    - The UNIX build system uses hardcoded "Zend/" directory
      names in a lot of places.  Might be solved by using mv(1)
      in buildconf.

    - The Win32 build system might rely on a specific dirname as
      well.

    So, we should get comfortable with the idea of having a Zend
    _and_ a ZendEngine2 dir at the same time(*).

    Thoughts?

    (*) disk space/network bw is not an issue, when the
        user-chosen branch of the unused engine is empty (e.g.
        the PHP_5 branch in Zend would be empty).

    - Sascha