[oe] proper way to report(?) conflicting files being installed?

[Robert P. J. Day]

  long story short, colleague was adding packages to a build and ran
into error wherein both of:

  * autoconf-archive
  * gnome-common

were trying to install a couple identical m4-related files. some
quick googling produced this:

  https://patchwork.openembedded.org/patch/142467/

with the self-evident solution being applied to gnome-common to
"uninstall" the two conflicting files:

--- a/meta-oe/recipes-gnome/gnome-common/gnome-common_3.18.0.bb
+++ b/meta-oe/recipes-gnome/gnome-common/gnome-common_3.18.0.bb
@@ -17,4 +17,15 @@  DEPENDS = ""
 FILES_${PN} += "${datadir}/aclocal"
 FILES_${PN}-dev = ""

+# ax_code_coverage.m4 and ax_check_enable_debug.m4 are in gnome-common only
+# because older versions of autoconf-archive didn't have them yet. Now they
+# are in autoconf-archive from OE-core. We depend on that below to ensure
+# that recipes which only depend on gnome-common still get them.
+do_install_append () {
+    rm -f ${D}${datadir}/aclocal/ax_code_coverage.m4
+    rm -f ${D}${datadir}/aclocal/ax_check_enable_debug.m4
+}
+RDEPENDS_${PN} += "autoconf-archive"
+DEPENDS_append_class-native = " autoconf-archive-native"
+

  it *appears* that solved the problem, which raises the question --
should this patch be applied to the current gnome-common recipe? that
patchwork entry dates back to 2017 ... should it have been applied at
some point?

rday