From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Dan Streetman <ddstreet@canonical.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Rafael David Tinoco <rafael.tinoco@canonical.com>
Subject: Re: [PATCHv2] configure: replace --enable/disable-git-update with --with-git-submodules
Date: Wed, 27 Jan 2021 16:23:52 +0000 [thread overview]
Message-ID: <20210127162352.GQ3653144@redhat.com> (raw)
In-Reply-To: <20210119172046.43869-1-ddstreet@canonical.com>
On Tue, Jan 19, 2021 at 12:20:46PM -0500, Dan Streetman wrote:
> Replace the --enable-git-update and --disable-git-update configure params
> with the param --with-git-submodules=(update|validate|ignore) to
> allow 3 options for building from a git repo.
>
> This is needed because downstream packagers, e.g. Debian, Ubuntu, etc,
> also keep the source code in git, but do not want to enable the
> 'git_update' mode; with the current code, that's not possible even
> if the downstream package specifies --disable-git-update.
>
> The previous parameters are deprecated but still available; the
> --enable-git-update parameter maps to --with-git-submodules=update and
> --disable-git-update parameter maps to --with-git-submodules=validate.
>
> The configure script behavior is slightly modified, where previously
> the dtc, capstone, and slirp submodules were not validated when
> --disable-git-update was specified (but were updated with git-update
> enabled), now they are validated when using --with-git-submodules=validate
> and are only ignored when using --with-git-submodules=ignore.
>
> Signed-off-by: Dan Streetman <ddstreet@canonical.com>
> ---
> v1: https://lists.gnu.org/archive/html/qemu-devel/2020-10/msg04799.html
> changes since v1:
> - add --help output explaining --with-git-submodules valid values
> - validate dtc, capstone, slirp submodules also
> - update commit description text
>
> Makefile | 24 ++-----------------
> configure | 51 ++++++++++++++++++++++++++++++----------
> scripts/git-submodule.sh | 34 ++++++++++++++++++++-------
> 3 files changed, 66 insertions(+), 43 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
I'll queue this with a batch of misc changes i have pending.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2021-01-27 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 17:20 [PATCHv2] configure: replace --enable/disable-git-update with --with-git-submodules Dan Streetman
2021-01-27 16:23 ` Daniel P. Berrangé [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210127162352.GQ3653144@redhat.com \
--to=berrange@redhat.com \
--cc=christian.ehrhardt@canonical.com \
--cc=ddstreet@canonical.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=rafael.tinoco@canonical.com \
/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 NNTP newsgroup(s).