Re: proper way to report(?) conflicting files being installed?

[Adrian Bunk <bunk@stusta.de>]

On Thu, Mar 19, 2020 at 09:22:54AM -0400, Robert P. J. Day wrote:
>...
> +# 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?

The currently implemented solution is:
# Default to enable autoconf-archive to avoid conflicts
PACKAGECONFIG ??= "autoconf-archive"
PACKAGECONFIG[autoconf-archive] = "--with-autoconf-archive, --without-autoconf-archive, autoconf-archive"

It is not clear to me why this gives the user to disable it
instead of unconditionally enabling it.

> rday

cu
Adrian