no man pages for pssh

[bryon@…]

$port installed | grep pssh
  pssh @2.3.1_0 (active)
$ man pssh
No manual entry for pssh
$ man pscp
No manual entry for pscp
$ man prsync
No manual entry for prsync
$ man pnuke
No manual entry for pnuke
$ man pslurp
No manual entry for pslurp

[mf2k (Frank Schima)]

In the future, please fill in the Port field and Cc the port maintainers (port info --maintainers pssh).

[cooljeanius (Eric Gallager)]

This reminds me, the pssh port conflicts with the port for putty (I have been meaning to file a ticket for that but never got around to it), and if pssh installed its manpages as well, that would be an additional point of conflict with the putty port. Well actually the pscp manpage would be the only one of them that would actually conflict, but that it is still an additional point of conflict that would need to be resolved.

[cooljeanius (Eric Gallager)]

Cc Me!

[kurthindenburg (Kurt Hindenburg)]

Cc Me!

[kurthindenburg (Kurt Hindenburg)]

I've been testing this - even if macports does install the man pages they will end up in /opt/local/Library/Frameworks/Python.framework/Versions/2.7/share/man/man1/ which is not in the MANPATH AFAIK there's no standard way to handle man files that all the different versions of python could install.

[drkp (Dan Ports)]

r122325

It might be that we should create a python.link_manpages to go along with python.link_binaries. I'm not sure if any other port currently needs it, though.