From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Fam Zheng <famz@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7 2/6] docker: don't rely on submodules existing in the main checkout
Date: Thu, 28 Sep 2017 13:03:41 -0500 [thread overview]
Message-ID: <723de7c1-e617-923c-6e69-561577f0fe1a@redhat.com> (raw)
In-Reply-To: <20170928120621.30288-3-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2675 bytes --]
On 09/28/2017 07:06 AM, Daniel P. Berrange wrote:
> When building the tarball to pass into the docker/vm test image,
> the code relies on the git submodules being checked out in the
> main checkout.
>
> ie if the developer has not run 'git submodule update --init dtc'
> many of the docker tests will fail due to the libfdt package not
'dtc' vs. 'libfdt' - is one of the acronyms wrong?
> being present in the test images. Patchew manually checks out the
> dtc submodule in the main git checkout, but this is a bad idea.
>
> When running tests we want to have a predictable set of submodules
> included in the source that's tested. The build environment is
> completely independant of the developers host OS, so the submodules
s/independant/independent/
> the developer has checked out should not be considered relevant for
> the tests.
>
> This changes the archive-source.sh script so that it clones the
> current git checkout into a temporary directory, checks out a
> fixed set of submodules, builds the tarball and finally removes
> the temporary git clone.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> scripts/archive-source.sh | 30 +++++++++++++++++++++++++++---
> 1 file changed, 27 insertions(+), 3 deletions(-)
>
> +++ b/scripts/archive-source.sh
> +# We want a predictable list of submodules for builds, that is
> +# independant of what the developer currently has initialized
and again
> +# in their checkout, because the build environment is completely
> +# different to the host OS.
> +submodules="dtc"
>
> if test $? -ne 0; then
> error "git submodule command failed"
> @@ -28,6 +34,21 @@ fi
>
> trap "status=$?; rm -f \"$list_file\"; exit \$status" 0 1 2 3 15
>
> +if git diff-index --quiet HEAD -- &>/dev/null
> +then
> + HEAD=HEAD
> +else
> + HEAD=`git stash create`
> +fi
> +git clone --shared . "$vroot_dir"
set -e is not in effect; do you need error checking here?
> +here=`pwd`
$PWD is cheaper than spawning a subprocess for `pwd`.
> +cd "$vroot_dir"
Definitely need error checking here.
> +git checkout $HEAD
> +
> +for sm in $submodules; do
> + git submodule update --init $sm
> +done
> +
> if test -n "$submodules"; then
> {
> git ls-files || error "git ls-files failed"
> @@ -48,4 +69,7 @@ fi
>
> tar -cf "$tar_file" -T "$list_file" || error "failed to create tar file"
>
> +cd "$here"
and again here
> +rm -rf "$vroot_dir"
> +
> exit 0
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-09-28 18:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 12:06 [Qemu-devel] [PATCH v7 0/6] Initial support for keycodemapdb GIT submodule Daniel P. Berrange
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 1/6] build: automatically handle GIT submodule checkout for dtc Daniel P. Berrange
2017-09-28 17:58 ` Eric Blake
2017-09-29 9:08 ` Daniel P. Berrange
2017-09-28 17:59 ` Eric Blake
2017-09-29 9:09 ` Daniel P. Berrange
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 2/6] docker: don't rely on submodules existing in the main checkout Daniel P. Berrange
2017-09-28 18:03 ` Eric Blake [this message]
2017-09-29 9:14 ` Daniel P. Berrange
2017-10-02 12:55 ` Peter Maydell
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 3/6] ui: add keycodemapdb repository as a GIT submodule Daniel P. Berrange
2017-09-28 18:22 ` Eric Blake
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 4/6] ui: convert common input code to keycodemapdb Daniel P. Berrange
2017-09-28 18:25 ` Eric Blake
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 5/6] ui: convert key events to QKeyCodes immediately Daniel P. Berrange
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 6/6] ui: don't export qemu_input_event_new_key Daniel P. Berrange
2017-09-28 12:20 ` [Qemu-devel] [PATCH v7 0/6] Initial support for keycodemapdb GIT submodule no-reply
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=723de7c1-e617-923c-6e69-561577f0fe1a@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=famz@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).