Rename dman in the Debian .deb package to prevent conflict with Debian package debian-goodies about tools HOT 2 OPEN

CC @ximion

from tools.

Debian doesn't impose any rules on externally created packages - there are best practices that make sense to be followed by external packagers as well though, and of course there's some information for upstream projects in general.

That said, if the package would go into Debian, the binary would have to be renamed in order for the package to be accepted into the distribution. We have a process for resolving name conflicts, but the result of that is often that none of the binaries keeps a generic name and both are renamed, or in case of a name transition between two unrelated packages, there has to be a Debian release with no package claiming the binary name before a new package can take it. That may result in a 6-year delay at worst before a name change is final (that's one of the reasons why the APT CLI tool was named "apt-get" for so long and "apt" only appeared at a late time).
IMHO challenging an existing name is really not worth the trouble, and dmanual would be just as descriptive - and that name isn't taken yet. That name could be kept when the package ends up in Debian, and you have the additional benefit that the external dmd package is installable on more Debian systems since the name clash is avoided.

(Btw, the only reason we don't have dmd or more D tools in Debian is lack of maintainers and helpers in the D team ;-) - Any help is appreciated, as I don't really have the time to push D further in Debian. I can help non-DDs maintain their packages within Debian though).

from tools.