description here is a workplan, not the role of the maintainer. https://www.gentoo.org/glep/glep-0068.html#maintainer-descriptions I suggest to drop the section. ================================ <maintainer type="project"> <email>wine@gentoo.org</email> <name>Wine</name> <description> This package must be kept in sync with repo/proj/wine repository. Any changes need to be run past the maintainer to ensure the two repositories are kept in sync. </description> Reproducible: Always
It's pretty standard to state that someone should be CC'd on bugs or similar things in the description field. Stating that changes need to be run past the maintainer to keep repos in sync isn't different, is it?
No, it also does not belong there technically. I understand the reason, why you need/want this and suggest to add this in a comment in the .ebuild. # This package must be kept in sync with repo/proj/wine repository. # Any changes need to be run past the maintainer to ensure the two # repositories are kept in sync. This is read by everyone who touches the ebuild. Someone who edits the ebuild would likely not read comments in the metadata. Fixed after go via IRC in commit 5262fb9708ac52e4ef838cd137407c783667d00b Author: Jonas Stein <jstein@gentoo.org> Date: Thu May 14 01:42:45 2020 +0200 app-emulation/wine-vanilla: Clean metadata Delete workflow explanation from the maintainer description in the metadata.xml file. Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Jonas Stein <jstein@gentoo.org>
