[OE-core] [PATCH 0/6 v2] Fix RPM4 regressions based on Pyro

[Mark Hatle]

On 8/16/17 8:34 AM, Richard Purdie wrote:
> On Tue, 2017-08-15 at 16:41 -0500, Mark Hatle wrote:
>> From the comments to the original patch, the only not addressed was
>> adding an OE self-test for this behavior.  I tried to do this, but I
>> don't see any existing tests that build a recipe and inspect the
>> results of the built package.  I'm not sure of any other way to
>> identify if things are working or not.
> oe-selftest can do this.
> 

Are there any examples?  I was looking there and simply didn't see any.  I saw
the packaging for instance exercised python interfaces, version comparison
tools, etc.. but nothing that built a recipe/package and then verified the
contents were 'correct'.

Ideally the test would be to fabricate something with a known set of file
dependencies, produce a package from it and then verify that the package
properly included those dependencies.

I had looked at just picking some random library out of the deploy directory,
and doing a pattern search on it's provides.. but I'm not sure that type of test
would be very robust.

--Mark