Re: cloning gnulib with --depth=2 option hangning

[John W. Eaton]

On 21-Apr-2011, Bruno Haible wrote:

| Hi John,
| 
| John W. Eaton wrote:
| > When I execute
| > 
| >   git clone --depth=2 git://git.sv.gnu.org/gnulib
| > 
| > as is done when running the bootstrap script for the first time, the
| > git process hangs.
| 
| Yes, for me too it hangs. (git version 1.6.3.2)
| 
| The documentation on savannah.gnu.org
| <https://savannah.gnu.org/git/?group=gnulib>
| recommends to do
| 
|   git clone git://git.savannah.gnu.org/gnulib.git
| 
| that is,
|   - no --depth option,
|   - use a .git suffix at the end.

OK, but the build-aux/bootstrap script distributed with gnulib
includes the code

  case ${GNULIB_SRCDIR--} in
  -)
    if git_modules_config submodule.gnulib.url >/dev/null; then
      echo "$0: getting gnulib files..."
      git submodule init || exit $?
      git submodule update || exit $?

    elif [ ! -d "$gnulib_path" ]; then
      echo "$0: getting gnulib files..."

      trap cleanup_gnulib 1 2 13 15

      shallow=
      git clone -h 2>&1 | grep -- --depth > /dev/null && shallow='--depth 2'
      git clone $shallow git://git.sv.gnu.org/gnulib "$gnulib_path" ||
        cleanup_gnulib

      trap - 1 2 13 15
    fi
    GNULIB_SRCDIR=$gnulib_path
    ;;

so it can invoke the command

  git clone --depth 2 git://git.sv.gnu.org/gnulib gnulib

Shouldn't the bootstrap script use the recommended way of cloning a
fresh copy of gnulib?

Oh, I see that the idea here is to avoid copying a lot of history that
might not be useful to people not actually working on gnulib.  In that
case, it would be great if the --depth option worked...  I seem to
recall that it did in the past, so maybe this is a savannah problem.

jwe