[Openembedded-architecture] [RFC] additions to new package submission and updates.

[Alexander Kanavin]

On 02/26/2018 06:40 PM, Joshua Watt wrote:
> Does it have to be in maintainers.inc? Could we just include 
> RECIPE_MAINTAINER in each recipe that actually has a maintainer (TBH, I 
> don't know *exactly* how it work...)?

I agree. I do want to get rid of maintainers.inc file, as it is clunky, 
awkward, and always out of date. Now that we have an automatic test for 
presence of maintainers, we should definitely move the assignments to 
recipes themselves.

As for upstream check stuff, UPSTREAM_CHECK_REGEX is only present in 
exceptional cases when the default regex does not work. It definitely is 
not required. It's something else that is missing here: only oe-core 
recipes are regularly tested for correctness of the check. Needs to be 
extended to other layers, if layer maintainers find such a 'check that 
upstream check works' useful.

You can run the tests for this metadata with this simple command:

oe-selftest -r distrodata

This would:
a) check that every recipe (in oe-core only; not other layers) has an 
assigned maintainer.
b) check that every recipe in every configured layer has a sane upstream 
version check: specifically that the upstream version can be determined, 
and if it cannot, that is explicitly acknowledged in the recipe.

Let me know if there's something else missing.


Alex