From: Fam Zheng <famz@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/6] tests/docker: add optional libs to travis.docker
Date: Mon, 31 Oct 2016 10:23:53 +0800 [thread overview]
Message-ID: <20161031022353.GG30303@lemon> (raw)
In-Reply-To: <20161028163339.31096-4-alex.bennee@linaro.org>
On Fri, 10/28 17:33, Alex Bennée wrote:
> In our .travis.yml we install a bunch of extra libraries which are not
> part of the packaged QEMU's builddeps. We include them here to make our
> docker container more closely match the state of the system after docker
> has installed the rest of the build dependencies.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> tests/docker/dockerfiles/travis.docker | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/tests/docker/dockerfiles/travis.docker b/tests/docker/dockerfiles/travis.docker
> index e4983ae..6bef722 100644
> --- a/tests/docker/dockerfiles/travis.docker
> +++ b/tests/docker/dockerfiles/travis.docker
> @@ -2,5 +2,12 @@ FROM quay.io/travisci/travis-ruby
> RUN apt-get update
> RUN apt-get -y build-dep qemu
> RUN apt-get -y build-dep device-tree-compiler
> -RUN apt-get -y install python2.7 dh-autoreconf
> +# Additional optional libs not in QEMU's builddep
> +RUN apt-get -y install libbrlapi-dev liblttng-ust-dev libcap-ng-dev \
> + libnfs-dev libnss3-dev libpixman-1-dev \
> + libpng12-dev librados-dev libseccomp-dev \
> + libspice-protocol-dev libspice-server-dev \
> + libssh2-1-dev liburcu-dev libusb-1.0-0-dev \
> + libvte-2.90-dev
> +RUN apt-get -y install python2.7 dh-autoreconf sparse
Any reason to use two apt-get lines?
Also, can you put these package names in $PACKAGES and dump 'dpkg -l $PACKAGES'
to /packages.txt like in ubuntu.docker? That way we can print it in reports by
adding SHOW_ENV=1 in make invocation.
Fam
> ENV FEATURES pyyaml
> --
> 2.10.1
>
>
next prev parent reply other threads:[~2016-10-31 2:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 16:33 [Qemu-devel] [PATCH 0/6] Expand the building of qemu-user docker images Alex Bennée
2016-10-28 16:33 ` [Qemu-devel] [PATCH 1/6] tests/docker/Makefile.include: fix diff-index call Alex Bennée
2016-10-31 2:19 ` Fam Zheng
2016-10-31 11:55 ` Alex Bennée
2016-11-01 10:02 ` Alex Bennée
2016-11-01 10:38 ` Fam Zheng
2016-11-01 11:41 ` Alex Bennée
2016-10-28 16:33 ` [Qemu-devel] [PATCH 2/6] tests/docker/test-user: a simple linux-user test Alex Bennée
2016-10-31 2:20 ` Fam Zheng
2016-10-28 16:33 ` [Qemu-devel] [PATCH 3/6] tests/docker: add optional libs to travis.docker Alex Bennée
2016-10-31 2:23 ` Fam Zheng [this message]
2016-10-28 16:33 ` [Qemu-devel] [PATCH 4/6] tests/docker/Makefile: Add a rule for Debian user images Alex Bennée
2016-10-28 16:33 ` [Qemu-devel] [PATCH 5/6] tests/docker/docker.py: expand images command Alex Bennée
2016-10-31 2:28 ` Fam Zheng
2016-10-28 16:33 ` [Qemu-devel] [PATCH 6/6] tests/docker/Makefile.include: expand docker help text Alex Bennée
2016-10-31 2:34 ` Fam Zheng
2016-10-31 2:41 ` [Qemu-devel] [PATCH 0/6] Expand the building of qemu-user docker images Fam Zheng
2016-10-31 11:40 ` Alex Bennée
2016-10-31 13:39 ` 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=20161031022353.GG30303@lemon \
--to=famz@redhat.com \
--cc=alex.bennee@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).