[OE-core] [PATCH 1/3] rpm: add support for remote package feeds via PACKAGE_FEED_URIS variable

[Ibarra Lopez, Humberto]

Yeah, it does sound off but we could use it. We could put a mock value in the ip to the PACKAGE_FEED_URIS var to build this image and once it boths update that value with the real one. We would have to check that the mock value was correctly set before updating so we can test the var being correctly set; and then check that the feeds are updated correctly once a valid ip is there. I will look into this.

Humberto

-----Original Message-----
From: Richard Purdie [mailto:richard.purdie at linuxfoundation.org] 
Sent: Wednesday, March 15, 2017 10:08 AM
To: Ibarra Lopez, Humberto <humberto.ibarra.lopez at intel.com>; Alexander Kanavin <alexander.kanavin at linux.intel.com>; Burton, Ross <ross.burton at intel.com>
Cc: OE-core <openembedded-core at lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/3] rpm: add support for remote package feeds via PACKAGE_FEED_URIS variable

On Wed, 2017-03-15 at 15:38 +0000, Ibarra Lopez, Humberto wrote:
> Sorry, missed the previous mail.
> 
> I am not sure how to improve the hardcoding there, I don't like it 
> either, but couldn't find an alternative. The thing is that we need 
> the ip of the host as seen from the target to run testimage, but we 
> don’t have the exact value for that one until qemu is up. The issue 
> here is that we need to give this ip to the conf in the 
> PACKAGE_FEED_URIS before building so we can get an image with this var 
> to later use in testimage.
> 
> If someone has a better idea to get rid of this hardcoding, it would 
> be great to know.

We could run a sed command inside the image after it boots but before triggering the tests to put the correct IP/port number into the file?

Not a perfect test but simple and probably good enough for this?

Cheers,

Richard