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

[Alexander Kanavin]

On 08/16/2017 06:37 PM, Mark Hatle wrote:
> 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.

How was this regression discovered in the first place? I guess that some 
recipe used to build without error with rpm5, and stopped building with 
rpm4. This is what you could test for: isolate the problematic bit, 
remove everything else, and write a simple recipe(s) that can be placed 
into meta-selftest. Then simply build those from the selftest; if they 
build without error, you don't need to do more sophisticated checks.


Alex