scripts/functions
changeset 788 cc9721772cc6
parent 787 0725d7f8ab22
child 799 a31e625eb343
     1.1 --- a/scripts/functions	Mon Aug 11 12:22:47 2008 +0000
     1.2 +++ b/scripts/functions	Tue Aug 12 07:47:19 2008 +0000
     1.3 @@ -445,8 +445,6 @@
     1.4              ;;
     1.5      esac
     1.6  
     1.7 -    CT_DoLog EXTRA "Retrieving '${file}'"
     1.8 -
     1.9      # Do we already have it?
    1.10      ext=$(CT_GetFileExtension "${file}" ${first_ext})
    1.11      if [ -n "${ext}" ]; then
    1.12 @@ -455,6 +453,7 @@
    1.13      fi
    1.14  
    1.15      # Try to retrieve the file
    1.16 +    CT_DoLog EXTRA "Retrieving '${file}'"
    1.17      CT_Pushd "${CT_TARBALLS_DIR}"
    1.18  
    1.19      if [ -n "${CT_LOCAL_TARBALLS_DIR}" ]; then
    1.20 @@ -570,7 +569,7 @@
    1.21          return 0
    1.22      fi
    1.23  
    1.24 -    CT_DoLog EXTRA "Extracting '${file}'"
    1.25 +    CT_DoLog EXTRA "Extracting and patching '${file}'"
    1.26      case "${ext}" in
    1.27          .tar.bz2)     CT_DoExecLog ALL tar xvjf "${full_file}";;
    1.28          .tar.gz|.tgz) CT_DoExecLog ALL tar xvzf "${full_file}";;
    1.29 @@ -593,8 +592,6 @@
    1.30  
    1.31      # Kludge: outside this function, we wouldn't know if we had just extracted
    1.32      # a libc addon, or a plain package. Apply patches now.
    1.33 -    CT_DoLog EXTRA "Patching '${file}'"
    1.34 -
    1.35      if [ "${libc_addon}" = "y" ]; then
    1.36          # Some addon tarballs directly contain the correct addon directory,
    1.37          # while others have the addon directory named after the tarball.