From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, alex.bennee@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2] docker: add installation to build tests
Date: Mon, 25 Sep 2017 11:11:03 +0200 [thread overview]
Message-ID: <caf7430e-6819-8c76-5a26-1fcbfc0a0b1a@redhat.com> (raw)
In-Reply-To: <20170925030912.GC22980@lemon.lan>
On 25/09/2017 05:09, Fam Zheng wrote:
> On Fri, 09/22 17:49, Paolo Bonzini wrote:
>> diff --git a/tests/docker/common.rc b/tests/docker/common.rc
>> index 6865689..1522aab 100755
>> --- a/tests/docker/common.rc
>> +++ b/tests/docker/common.rc
>> @@ -36,3 +36,11 @@ build_qemu()
>> $QEMU_SRC/configure $config_opts
>> make $MAKEFLAGS
>> }
>> +
>> +install_qemu()
>> +{
>> + make install $MAKEFLAGS DESTDIR=$PWD/=destdir
>
> Why provide DESTDIR? build_qemu already has "--prefix=$INSTALL_DIR", can a
> simple "make install $MAKEFLAGS" work? Is there a permission problem?
Just to test the $DESTDIR case. I have plans to extend the test a bit
further, such as:
- checking that $INSTALL_DIR remains empty
- comparing the destdir installation against the $INSTALL_DIR (to ensure
that the destdir doesn't end up in the installed files; distro packaging
conventions usually don't like that).
- doing the DESTDIR install as a non-root user
>> + ret=$?
>> + rm -rf $PWD/=destdir
>
> Why is this cleanup needed given the container will go away anyway?
Again it's just for cleanliness. Another possible test to add is that
"make distclean" actually leaves the build tree in a pristine state, and
this would fail if we leave the installation tree around.
All these tests, by the way, are inspired by the "make distcheck"
produced by Automake.
Paolo
next prev parent reply other threads:[~2017-09-25 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 15:49 [Qemu-devel] [PATCH v2] docker: add installation to build tests Paolo Bonzini
2017-09-25 3:09 ` Fam Zheng
2017-09-25 9:11 ` Paolo Bonzini [this message]
2017-09-25 11:14 ` Fam Zheng
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=caf7430e-6819-8c76-5a26-1fcbfc0a0b1a@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=famz@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).