From: Saul Wold <sgw@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
"Stanacar, StefanX" <stefanx.stanacar@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] testimage: dont use DNS lookup for qemu based testimages
Date: Wed, 19 Mar 2014 13:06:51 -0700 [thread overview]
Message-ID: <5329F8DB.8030306@linux.intel.com> (raw)
In-Reply-To: <1803761.bM8W6F0XkC@peggleto-mobl5.ger.corp.intel.com>
On 03/19/2014 06:17 AM, Paul Eggleton wrote:
> On Wednesday 19 March 2014 12:23:37 Stanacar, StefanX wrote:
>> On Tue, 2014-03-18 at 17:31 -0700, Saul Wold wrote:
>>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>>> ---
>>>
>>> meta/classes/testimage.bbclass | 10 ++++++++++
>>> 1 file changed, 10 insertions(+)
>>>
>>> diff --git a/meta/classes/testimage.bbclass
>>> b/meta/classes/testimage.bbclass index 691c7f6..ee028e1 100644
>>> --- a/meta/classes/testimage.bbclass
>>> +++ b/meta/classes/testimage.bbclass
>>> @@ -45,6 +45,16 @@ TESTIMAGEDEPENDS_qemuall =
>>> "qemu-native:do_populate_sysroot qemu-helper-native:d>
>>> TESTIMAGELOCK = "${TMPDIR}/testimage.lock"
>>> TESTIMAGELOCK_qemuall = ""
>>>
>>> +IMAGE_POSTPROCESS_COMMAND_qemuall += "fix_dns_lookup_for_qemu"
>>> +
>>
>> I might be wrong, but this won't have any effect with the default
>> (manual) way we use testimage. The testimage class isn't in the global
>> inherit, so that IMAGE_POSTPROCESS_COMMAND won't run as the image isn't
>> reconstructed.
>>
>> The AB does: bitbake core-image-sato on one step and then adds INHERIT
>> +="testimage" in local.conf in the next step and runs bitbake
>> core-image-sato -c testimage, no more do_rootfs here.
>>
>> As it this it will only work with testimage-auto when you have
>> TEST_IMAGE="1" in local.conf in the first build step so you only need to
>> do bitbake core-image-sato and do_testimage gets run after do_rootfs,
>> but we don't use this. And the fix should work for running the task
>> manually too.
>
> I have to say I agree; this is not the right fix.
>
Is there any reason that we can't include the INHERIT += "testimage"
during the core build?
The other choice is to move the function into the openssh recipe and
then the actual setting of the IMAGE_POSTPROCESS_COMMAND can happen in
the local.conf or auto.conf
>> I liked v1, I don't really see what the problem was there. No mattter
>> the way you run our qemu images, you still have to set a proper DNS, and
>> have network connectivity in the image (which usually involves the host
>> too) so defaulting to UseDNS no for qemu images seems a sensible default
>> to me.
>
> Well, v1 was unconditional in the openssh recipe; I think it still needs to be
> just for qemuall.
>
It was originally for qemuall, but was also for all images and was to
broad as some may not want it disabled in this way.
Further thoughts?
Sau!
> Cheers,
> Paul
>
next prev parent reply other threads:[~2014-03-19 20:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 0:31 [PATCH v2] testimage: dont use DNS lookup for qemu based testimages Saul Wold
2014-03-19 11:20 ` Koen Kooi
2014-03-19 12:23 ` Stanacar, StefanX
2014-03-19 13:17 ` Paul Eggleton
2014-03-19 20:06 ` Saul Wold [this message]
2014-03-19 21:43 ` Flanagan, Elizabeth
2014-03-19 22:57 ` Paul Eggleton
2014-03-19 21:44 ` Richard Purdie
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=5329F8DB.8030306@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=stefanx.stanacar@intel.com \
/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