Both sys-apps/compare and media-gfx/imagemagick create /usr/bin/compare (and the corresponding manpage. This means one ebuild will overwrite the other. It can be fixed by modifying the sys-apps/compare ebuild to install to use a different name, say compare-binary.
either change the package compare or we can add blockers, doesnt matter much to be either way ... how about you Stuart ?
I'm happy for us to add blockers. Best regards, Stu
Blocker added. Best regards, Stu
Stuart, this doesn't suffice. Please make sure that you always block packages mutually. Right now you can still inatll imagemagick, despite having compare installed.
Also, I would say that blockers isn't a solution. Because imagemagick is such a common application, this has the effect of stopping most people using compare. You might as well just remove compare from portage and call it a bug fix. It would be so simple to have the compare ebuild simply use another binary name, as the sys-apps/rename ebuild does (it installs as /usr/bin/renamexm to avoid conflict with sys-apps/util-linux). To make it easier, here is the code that I think should be put into the compare ebuild: src_install() { OBJ=${PN}/OBJ/`ls ${PN}/OBJ` dobin ${OBJ}/${PN} binary-compare || die doman ${PN}/${PN}.1 binary-compare.1 } pkg_postinst() { ewarn "This has been renamed to 'binary-compare' to avoid" ewarn "a naming conflict with media-gfx/imagemagick." }
Carlo: imagemagick isn't my package. I've reassigned to the graphics herd, for them to add the blocker to imagemagick. Rodrigo: $UPSTREAM calls the installed file 'compare'. If you'd like to see it installed with a different name, please convince them to adopt a change first. Best regards, Stu
fixed in imagemagick-6.2.9.5
