Currently, at least on Mac OS X, the Radmind man pages are installed in /usr/local/man. Based on some research, I would suggest changing this destination directory.
1. According to the Filesystem Hierarchy Standard, /usr/local/man and /usr/local/share/man should be the same directory. That standard suggests that /usr/local/man may be considered deprecated in the future (after version 2.3 of the FSH), and that it should be a symlink which links to /usr/local/share/man.
There is slightly conflicting information about this in version 2.3 of the standard but these links support the move to /usr/local/share/man:
"The requirements for the contents of this directory are the same as /usr/share. The only additional constraint is that /usr/local/share/man and /usr/local/man directories must be synonomous (usually this means that one of them must be a symbolic link)."
2. In Mac OS X, an examination of /private/etc/man.conf indicates that were the Radmind man pages to be relocated to /usr/local/share/man, they ought to be accessible by default when using the `man` utility. By placing them in this directory rather than /usr/local/man, the default man.conf configuration would pick up on them and they would be in $MANPATH out of the box.
Because of the current install location on Mac OS X, the Radmind man pages are not in the default $MANPATH constructed by man.conf. Systems administrators will either need to make per-user configuration changes, overload system-wide changes to shell configuration files, or overload /private/etc/man.conf itself. The least apparent change is probably the man.conf one, but it helpfully affects all shells that use `/usr/libexec/path_helper` to construct $MANPATH.