From: "Gary V. Vaughan" <gary@vaughan.pe>
To: "Tim Rühsen" <tim.ruehsen@gmx.de>
Cc: bug-gnulib@gnu.org
Subject: Re: bootstrap regression ?
Date: Sat, 2 Mar 2019 08:52:42 -0800 [thread overview]
Message-ID: <E16F1841-1488-44B5-9A35-85E81F490003@vaughan.pe> (raw)
In-Reply-To: <546d9ab2-4a2d-9a63-7ee6-8c076fc98571@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
> On Mar 1, 2019, at 1:42 PM, Tim Rühsen <tim.ruehsen@gmx.de> wrote:
>
> Hi,
>
> at GnuTLS we have one git submodule that is not 'active' by default -
> this is on purpose since we want to init it just in certain cases.
>
> The latest 'bootstrap' script doesn't accept this and stops with an error:
> "./bootstrap: some git submodules are not initialized. Run 'git
> submodule init' and bootstrap again."
>
> The breaking change in 'bootstrap' is:
>
> +# Don't proceed if there are uninitialized submodules. In particular,
> +# the next step will remove dangling links, which might be links into
> +# uninitialized submodules.
> +#
> +# Uninitialized submodules are listed with an initial dash.
> +if $use_git && git submodule | grep '^-' >/dev/null; then
> + die "some git submodules are not initialized. " \
> + "Run 'git submodule init' and bootstrap again."
> +fi
>
> Currently I just commented out these lines, but a proper mechanism would
> be nice.
Hi Tim,
Have you considered this?
https://github.com/gnulib-modules/bootstrap
It has proven invaluable for incorporating gnulib modules into libtool, M4 and several other projects with more complex bootstrap processes than the standard gnulib bootstrap scripts can accommodate cleanly...
Cheers,
Gary
[-- Attachment #2: Type: text/html, Size: 2119 bytes --]
next prev parent reply other threads:[~2019-03-02 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 21:42 bootstrap regression ? Tim Rühsen
2019-03-02 16:52 ` Gary V. Vaughan [this message]
2019-03-02 18:08 ` Tim Rühsen
2019-03-02 23:00 ` Gary V. Vaughan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16F1841-1488-44B5-9A35-85E81F490003@vaughan.pe \
--to=gary@vaughan.pe \
--cc=bug-gnulib@gnu.org \
--cc=tim.ruehsen@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).