On Sun, May 27, 2018 at 10:17:40PM +0200, Bruno Haible wrote:
> I've pushed both patches in your name now.
>
> Had to adapt them a bit because the file 'build-aux/bootstrap' had been
> reindented meanwhile.
Thanks!
--
Colin Watson [cjwat...@debian.org]
Colin Watson wrote:
> In the following message there's an
> additional commit that adds what I think is reasonable documentation of
> this; comments welcome. This is intended to be applied on top of my
> previous patch in
> https://lists.gnu.org/archive/html/bug-gnulib/2018-04/msg00029.html,
> whi
On Mon, Apr 09, 2018 at 01:12:14PM +0200, Bruno Haible wrote:
> What I'm saying is that code changes that offer more choice to the user
> should be accompanied with documentation changes, so that the user is
> aware of the choices that you offer them.
>
> Guessing what are the possible choices, by
Hi Colin,
> 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.
Ah, I sa
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
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/
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 GNULI
