Created attachment 369692 [details] build.log * Detected file collision(s): * * /usr/bin/makecert * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-lang/mono-3.2.3:0::gentoo * /usr/bin/makecert * * Package 'net-libs/czmq-2.0.3' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message.
Created attachment 379682 [details] CZMQ build renaming makecert to czmq_makecert This updated ebuild renames makecert to czmq_makecert. Note that I don't know if there's a policy about what name to choose or what is the best way to do it. The ebuild just mv makecert to czmq_makecert with this nifty elog "To avoid colliding with Mono, this package's makecert utility was renamed czmq_makecert."
Created attachment 379684 [details, diff] Updated CZMQ ebuild patch Updated as patch against portage czmq-2.2.0 ebuild
Created attachment 379686 [details, diff] Updated CZMQ ebuild patch Seems like the missing version.sh in 2.1.0 is still missing in 2.2.0. Included fix is from 2.1.0 ebuild. https://bugs.gentoo.org/show_bug.cgi?id=508864
What is mono's "makecert" good for?
It serves as an equivalent to .NET SDK's makecert.exe tool. It is used to generate assembly signing certificates, including self-signed. Perhaps OpenSSL might be used as an alternative, but I don't know how well it plays with authenticode and god knows what, as this might have some specific magic OIDs relating to MS approved code signature schemes. Also, it means that .NET samples can be used as-is with Mono. On the other hand, https://developer.mozilla.org/en/docs/Signing_an_executable_with_Authenticode and http://sourceforge.net/projects/osslsigncode/ provides documentation/tools to do such without. So to sum up, I have no idea if renaming the program is a better idea than exluding one or the other.
+*czmq-2.2.0-r2 (15 Sep 2014) + + 15 Sep 2014; Justin Lecher <jlec@gentoo.org> +czmq-2.2.0-r2.ebuild: + Avoid file collisions, #500476 +
