[Openembedded-architecture] [openembedded-architecture] Recipe maintainers

[Alexander Kanavin]

On 03/19/2018 07:19 AM, Khem Raj wrote:
> This is a fine idea. Instead of creating separate file, it would be best 
> to maintain this information in recipe header itself, because when 
> someone is working on a recipe then he/she can get all needed 
> information in one place. Alpine project does it this way and Arch 
> project does it too e.g. see
> 
> https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/gcc 
> 
> 
> https://git.alpinelinux.org/cgit/aports/tree/main/musl/APKBUILD
> 
> see the following portion in particular.
> 
> # Maintainer:  name <email>
> # Contributor: name <email>
> 
> We might make Contributor field optional or may be ignore it completely 
> but we can adopt Maintainer field.
> 
> 
> Maintaining a maintainer file is also a hassle in itself, we quite often 
> patch it in OE-core too. But moving this information into recipe itself 
> in a consistent way would be a good approach IMO, consist format would 
> mean we can run tools over it to grok this info and also add sanity 
> tests of information is missing e.g.

For what it's worth, I firmly support getting rid of maintainer.inc 
file, and splitting it into individual recipes. Unfortunately, RP wasn't 
convinced. But maybe we can still persuade him? :)

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12573#c2


As for sanity tests, I added a test recently that checks for recipes 
without maintainers. Just run:

oe-selftest -r distrodata

and it will tell you.


Alex