Hi Eric, Bruno,
On Tue, 16 Mar 2010, Eric Blake wrote:
> Indeed, bison already uses multiple submodules (gnulib and autoconf),
> and has done for more than a year. It may be worth getting Joel's
> opinions here, as the maintainer of the only GNU package that I am aware
> of that currently tracks
Bruno Haible wrote:
> As I understand it, 'bootstrap' currently updates all submodules when it
> wants to update only the gnulib submodule. What about packages that will have
> other submodules? Here is a proposed fix:
>
> 2010-03-14 Bruno Haible
>
> * build-aux/bootstrap: Apply "git submo
On 03/16/2010 04:16 AM, Bruno Haible wrote:
> Hi Eric,
>
>> What's the use case for updating some, but not all, submodules?
>
> Imagine a package that has submodules 'gnulib', 'libxml', 'libcroco'
> (like GNU gettext might have). It would be perfectly normal for the
> developer to stay with the l
Hi Eric,
> What's the use case for updating some, but not all, submodules?
Imagine a package that has submodules 'gnulib', 'libxml', 'libcroco'
(like GNU gettext might have). It would be perfectly normal for the
developer to stay with the last known good libxml and libcroco but
try the newest gnu
On 03/14/2010 07:14 AM, Bruno Haible wrote:
> Hi Eric,
>
> As I understand it, 'bootstrap' currently updates all submodules when it
> wants to update only the gnulib submodule.
Correct.
> What about packages that will have
> other submodules?
What's the use case for updating some, but not all,
Hi Eric,
As I understand it, 'bootstrap' currently updates all submodules when it
wants to update only the gnulib submodule. What about packages that will have
other submodules? Here is a proposed fix:
2010-03-14 Bruno Haible
* build-aux/bootstrap: Apply "git submodule" commands only
