> These packages don't conflict; they merely provide the same > service. There is no reason that these three packages cannot > coexist on the same system. Any namespace overlap can be > solved by alternatives or renaming, as such things are normally > rectified. > Debian policy should proscribe such inconveniences.
Okay, then solve the problem of which one should actually work on the standard port? You can't use update-alternatives if the software is launched in a different manner. If you have such an advanced setup, it isn't really that hard to build it yourself, or use --force.
