Running into following collisions between these two packages: * sys-devel/autoconf-archive-2015.02.04 * gnome-base/gnome-common-3.14.0 Following files are clashing: * gnome-base/gnome-common-3.14.0:3::gentoo * /usr/share/aclocal/ax_check_enable_debug.m4 * /usr/share/aclocal/ax_code_coverage.m4
Why would gnome-base/gnome-common install ax_* files?
CC-ing the second package maintainers and QA. I'd really prefer if we found solution other than making gnome-common depend on autoconf-archive :).
(In reply to Jeroen Roovers from comment #1) > Why would gnome-base/gnome-common install ax_* files? Because gnome's autoconf macros in gnome-common.m4 and gnome-code-coverage.m4 require AX_CHECK_ENABLE_DEBUG and AX_CODE_COVERAGE, and until a few days ago we didn't have anything reasonable in portage that provided ax_check_enable_debug.m4 and ax_code_coverage.m4 on which gnome-common could depend. I see three possible solutions here: (1) split out ax_check_enable_debug.m4 and ax_code_coverage.m4 into a separate ebuild on which both autoconf-archive and gnome-common will depend; (2) make gnome-common depend on autoconf-archive (but mgorny doesn't like it, so let's try to avoid this :) (3) add "autoconf-archive" to gnome-common's IUSE that adds a dependency on new >=autoconf-archive-2015.02.04 and doesn't install ax_*.m4 files.
splitting autoconf-archive doesn't make sense. it owns the ax_* namespace. the files GNOME is installing even refers to the autoconf-archive project. just renaming the files to like gnome_xxx won't work because the macros exported will have the same name but will fall out of sync. you could rename the files if you also renamed the macros. then again, this package is all of 2MiB. a dep on it isn't a big deal.
Fair enough. Hopefully this will satisfy everybody: +*gnome-common-3.14.0-r1 (17 Feb 2015) + + 17 Feb 2015; Alexandre Rostovtsev <tetromino@gentoo.org> + gnome-common-3.14.0.ebuild, +gnome-common-3.14.0-r1.ebuild, metadata.xml: + Fix file collision with new sys-devel/autoconf-archive versions; + USE=autoconf-archive pulls in autoconf-archive as a dependency, + USE=-autoconf-archive blocks it (bug #540138, thanks to Priit Laes et al). + 17 Feb 2015; Alexandre Rostovtsev <tetromino@gentoo.org> + autoconf-archive-2015.02.04.ebuild: + File collision with gnome-common, bug #540138 Note: since future gnome-common versions may need to unconditionally depend on autoconf-archive, I had to revbump gnome-common and give autoconf-archive a dependency on !>=gnome-base/gnome-common-3.14.0-r1[-autoconf-archive(+)]
