Installed binary name conflict in Debian

[nc7s]

As is reported in Debian bug #1099838, this bacon installs to /usr/bin/bacon, which the unrelated package ruby-bacon also does.

Debian Policy section 10 "Files", more specifically its first subsection 10.1 "Binaries", opens with

Two different packages must not install programs with different functionality but with the same filenames.

Thus we must solve this through negotiation with the maintainers of the ruby-bacon package, as per the same paragraph:

If this case happens, one of the programs must be renamed. The maintainers should report this to the debian-devel mailing list and try to find a consensus about which program will have to be renamed. If a consensus cannot be reached, both programs must be renamed.

To be noted, however, is this only affects the name of the binary installed from the Debian package.

[Canop]

Note: this was discussed on Miaou before we decided to create an issue for visibility.

My current position (which is expected to change following feedback):

• I don't want to bother the maintainers of the older ruby-bacon package and ask them to rename their binary unless it's clear it's a dying program (I don't know it). They were first.
• Having bacon holding a different name depending on how it was installed seems inconvenient
• if nothing else works, having no deb package for bacon doesn't look catastrophic, as cargo is the prefered install solution

[nc7s]

I don't know if this counts as "dying", but its last code change happened in 2017, and it's officially announced to have development "halted". The last contentful Debian upload happened in 2018, then there's only one NMU for rebuilds.