Re: ./bootstrap --gnulib-srcdir and GNULIB_REVISION

[Simon Josefsson]

Simon Josefsson via Gnulib discussion list <bug-gnulib@gnu.org> writes:

> My reaction was initially exactly the same as yours, until I found this
> piece of --help documentation, which actually is the first (and
> presumably highest priority) rule:
>
>  * If the environment variable GNULIB_SRCDIR is set (either as an
>    environment variable or via the --gnulib-srcdir option), then sources
>    are fetched from that local directory.  If it is a git repository and
>    the configuration variable GNULIB_REVISION is set in bootstrap.conf,
>    then that revision is checked out.
>
> So I think this combination is intended to be supported, it is just not
> working when a .gitmodules file is present in $CWD -- something that is
> not mentioned as a requirement.

Sorry, I found this piece of --help contradict the last sentence I wrote:

  If you maintain a package and want to pin a particular revision of the
  Gnulib sources that has been tested with your package, then there are
  two possible approaches: either configure a 'gnulib' submodule with the
  appropriate revision, or set GNULIB_REVISION (and if necessary
  GNULIB_URL) in bootstrap.conf.

So it seems having a git submodule for gnulib and using GNULIB_REVISION
at the same time is not supported.

FWIW, I'm going to experiment in libntlm and use GNULIB_REVISION in
bootstrap.conf instead of a git submodule, to allow a downloaded tarball
of git HEAD to be a supported way of building the package from source.
This hasn't worked historically for reasons discussed in this thread,
but given the xz backdoor I think there is value in supporting this
approach.

/Simon

signature.asc
Description: PGP signature