From 6bb5ff7137b2582211c76bb6c87cd7f939c80eba Mon Sep 17 00:00:00 2001 From: Ilia Alshanetsky Date: Mon, 1 Dec 2003 21:37:35 +0000 Subject: The least intrusive way to 'import' PECL extensions into the main tree. For the moment this deals with tidy, further extensions can be added at a later point. --- buildconf | 31 ++++++++++++++++++++++--------- 1 file changed, 22 insertions(+), 9 deletions(-) diff --git a/buildconf b/buildconf index 95aa69c1ba..c71df1f9e1 100755 --- a/buildconf +++ b/buildconf @@ -12,19 +12,32 @@ case "$EXTRA_VERSION" in esac devok=0 +pecl_args=0 -while test $# -gt 0; do - if test "$1" = "--copy"; then - automake_flags=--copy - fi +# Import 'gold' extensions from PECL +GOLDEN='tidy' - if test "$1" = "--force"; then - devok=1 - echo "Forcing buildconf" - fi +for i in $*; do + if test "$i" = "--pecl-import"; then + pecl_args=1 + elif test "$i" = "--copy"; then + automake_flags=--copy + pecl_args=0 + elif test "$i" = "--force"; then + devok=1 + echo "Forcing buildconf" + pecl_args=0 + elif test $pecl_args -eq 1; then + # Allow the developer to specify some custom PECL extensions to fetch + GOLDEN=$GOLDEN" "$i + fi +done; - shift +cd ext; +for ext in $GOLDEN; do + cvs co -d $ext pecl/$ext; done +cd ..; if test "$dev" = "0" -a "$devok" = "0"; then echo "You should not run buildconf in a release package." -- cgit v1.2.1