From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] configure: add sanity check to catch builds from "git archive"
Date: Thu, 28 Jun 2018 14:13:11 +0100 [thread overview]
Message-ID: <20180628131311.GA13361@redhat.com> (raw)
In-Reply-To: <20180418171151.5263-1-berrange@redhat.com>
Opps, forgot to CC Paolo on this patch for the "misc" queue.
On Wed, Apr 18, 2018 at 06:11:51PM +0100, Daniel P. Berrangé wrote:
> The "git archive" feature creates tarballs which are missing all
> submodule content. GitHub unhelpfully provides users with "Download"
> links that claim to give them valid source release tarballs. These
> GitHub archives will not be buildable as they are created by the
> "git archive" feature and so are missing content. The user gets
> unhelpful messages from make such as:
>
> fatal error: ui/input-keymap-atset1-to-qcode.c: No such file or directory
>
> By adding a sanity check we can give users an informative message about
> what they've done wrong.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> configure | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/configure b/configure
> index 0a19b033bc..089b00068c 100755
> --- a/configure
> +++ b/configure
> @@ -296,6 +296,24 @@ then
> else
> git_update=no
> git_submodules=""
> +
> + if ! test -f "$source_path/ui/keycodemapdb/README"
> + then
> + echo
> + echo "ERROR: missing file $source_path/ui/keycodemapdb/README"
> + echo
> + echo "This is not a GIT checkout but module content appears to"
> + echo "be missing. Do not use 'git archive' or GitHub download links"
> + echo "to acquire QEMU source archives. Non-GIT builds are only"
> + echo "supported with source archives linked from:"
> + echo
> + echo " https://www.qemu.org/download/"
> + echo
> + echo "Developers working with GIT can use scripts/archive-source.sh"
> + echo "if they need to create valid source archives."
> + echo
> + exit 1
> + fi
> fi
> git="git"
>
> --
> 2.14.3
>
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 :|
next prev parent reply other threads:[~2018-06-28 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 17:11 [Qemu-devel] [PATCH v2] configure: add sanity check to catch builds from "git archive" Daniel P. Berrangé
2018-04-18 17:54 ` Cornelia Huck
2018-04-19 17:31 ` Philippe Mathieu-Daudé
2018-06-28 13:13 ` Daniel P. Berrangé [this message]
2018-06-29 13:55 ` Paolo Bonzini
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=20180628131311.GA13361@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--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).