scripts/functions: cvs retrieval first tries the mirror for tarballs

The cvs download helper looks for the local tarballs dir to see if it
can find a pre-downloaded tarball, and if it does not find it, does
the actual fetch to upstream via cvs.

In the process, it does not even try to get a tarball from the local
mirror, which can be useful if the mirror has been pre-populated
manually (or with a previously downloaded tree).

Fake a tarball get with the standard tarball-download helper, but
without specifying any upstream URL, which makes the helper directly
try the LAN mirror.

Of course, if no mirror is specified, no URL wil be available, and
the standard cvs retrieval will kick in.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

# Build script for m4

CT_M4_VERSION=1.4.13

do_companion_tools_m4_get() {

    CT_GetFile "m4-${CT_M4_VERSION}" \

               {ftp,http}://ftp.gnu.org/gnu/m4

}

do_companion_tools_m4_extract() {

    CT_Extract "m4-${CT_M4_VERSION}"

    CT_Patch "m4" "${CT_M4_VERSION}"

}

do_companion_tools_m4_build() {

    CT_DoStep EXTRA "Installing m4"

    mkdir -p "${CT_BUILD_DIR}/build-m4"

    CT_Pushd "${CT_BUILD_DIR}/build-m4"

    CT_DoExecLog CFG \

    "${CT_SRC_DIR}/m4-${CT_M4_VERSION}/configure" \

        --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"

    CT_DoExecLog ALL make

    CT_DoExecLog ALL make install

    CT_Popd

    CT_EndStep

}