On Mon, Apr 09, 2018 at 11:43:54AM +0200, Bruno Haible wrote:
> Hi Colin,
> > Some projects prefer to avoid git submodules for various reasons (they
> > have rather strange UI), but at present they're the only way to pin a
> > particular gnulib commit.  Add a couple of extra variables which can be
> > set in bootstrap.conf to control this separately.
> > 
> > * build-aux/bootstrap: Honour GNULIB_URL and GNULIB_REVISION in
> > bootstrap.conf when fetching gnulib using "git clone" or via
> With this change, the question "Which command-line options should I pass
> to 'bootstrap', and which environment variables should I set before
> invoking bootstrap?" has more than a single-sentence answer.

I don't understand why that is.  These are intended to be variables that
a project can set in bootstrap.conf (the same way that projects in
languages that have package managers often pin particular versions of
their dependencies that they've tested), not command-line options or
environment variables.  I intended this to be nothing more than a way to
control the things that you can already control by way of .gitmodules,
except without having to use git submodules with all their little

If something I did led you to believe these were intended as
command-line options or as environment variables, then please tell me

The question "Which variables may I set in bootstrap.conf?" already has
much more than a single-sentence answer ...


Colin Watson                                       [cjwat...@debian.org]

Reply via email to