From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: famz@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for 2.10 v2 5/6] docker: don't install device-tree-compiler build-deps in travis.docker
Date: Tue, 25 Jul 2017 15:39:41 +0100 [thread overview]
Message-ID: <87inigeg2a.fsf@linaro.org> (raw)
In-Reply-To: <37c12235-eec1-b960-6053-0414ebac0aae@amsat.org>
Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> On 07/25/2017 10:34 AM, Alex Bennée wrote:
>> Installing the device-tree-compiler build-deps is a little extreme. We
>> only actually need the binary so include it with the other packages.
>>
>> Suggested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> before:
>
> $ docker images qemu:travis --no-trunc
> --format="{{.Repository}}:{{.Tag}}\t{{.Size}}"
>
> qemu:travis 6.16GB
>
> after:
>
> qemu:travis 5.92GB
>
> not a big win :(
>
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>
> (not a "bugfix" btw)
It's arguable - it was certainly wrong as we just need the compiler and
I'm not sure build-dep actually would have pulled it on (although the
qemu build-dep probably does).
>
>> ---
>> tests/docker/dockerfiles/travis.docker | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/tests/docker/dockerfiles/travis.docker b/tests/docker/dockerfiles/travis.docker
>> index 636fa590a5..57ac8e1419 100644
>> --- a/tests/docker/dockerfiles/travis.docker
>> +++ b/tests/docker/dockerfiles/travis.docker
>> @@ -1,6 +1,5 @@
>> 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 python-yaml dh-autoreconf gdb strace lsof net-tools
>> +RUN apt-get -y install device-tree-compiler python2.7 python-yaml dh-autoreconf gdb strace lsof net-tools
>> ENV FEATURES pyyaml
>>
--
Alex Bennée
next prev parent reply other threads:[~2017-07-25 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 13:34 [Qemu-devel] [PATCH for 2.10 v2 0/6] Various docker fixes Alex Bennée
2017-07-25 13:34 ` [Qemu-devel] [PATCH for 2.10 v2 1/6] docker: ensure NOUSER for travis images Alex Bennée
2017-07-25 13:34 ` [Qemu-devel] [PATCH for 2.10 v2 2/6] docker: fix dirty/stash detection on some systems Alex Bennée
2017-07-25 13:34 ` [Qemu-devel] [PATCH for 2.10 v2 3/6] docker: ignore submodules when checking diff Alex Bennée
2017-07-25 13:34 ` [Qemu-devel] [PATCH for 2.10 v2 4/6] docker: docker.py make --no-cache skip checksum test Alex Bennée
2017-07-25 13:34 ` [Qemu-devel] [PATCH for 2.10 v2 5/6] docker: don't install device-tree-compiler build-deps in travis.docker Alex Bennée
2017-07-25 14:17 ` Philippe Mathieu-Daudé
2017-07-25 14:28 ` Philippe Mathieu-Daudé
2017-07-25 14:39 ` Alex Bennée [this message]
2017-07-25 13:34 ` [Qemu-devel] [PATCH for 2.10 v2 6/6] docker: reduce noise when building travis.docker Alex Bennée
2017-07-25 14:18 ` Eric Blake
2017-07-25 14:25 ` Philippe Mathieu-Daudé
2017-08-31 6:59 ` [Qemu-devel] [PATCH for 2.10 v2 0/6] Various docker fixes Fam Zheng
2017-09-05 7:54 ` Alex Bennée
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=87inigeg2a.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=famz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.