bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: "Tim Rühsen" <tim.ruehsen@gmx.de>
To: bug-gnulib@gnu.org
Subject: bootstrap regression ?
Date: Fri, 1 Mar 2019 22:42:57 +0100	[thread overview]
Message-ID: <546d9ab2-4a2d-9a63-7ee6-8c076fc98571@gmx.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 897 bytes --]

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.

Regards, Tim


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-03-01 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 21:42 Tim Rühsen [this message]
2019-03-02 16:52 ` bootstrap regression ? Gary V. Vaughan
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=546d9ab2-4a2d-9a63-7ee6-8c076fc98571@gmx.de \
    --to=tim.ruehsen@gmx.de \
    --cc=bug-gnulib@gnu.org \
    /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).