pam_krb5: Fix manual page in MIT case

[des]

Summary

• Always install the manual page as pam_krb5(8) regardless of which version we're using.
• Regenerate it using pod2mdoc instead of pod2man so it doesn't claim to be part of “User Contributed Perl Documentation”.
• Put the correct section number in the header and footer.
• Don't cross-reference non-existent pam(7) manual page.

[ivy]

lib/libpam/modules/pam_krb5/Makefile

79

i don't quite follow this. when would this not exist?

[cperciva]

lib/libpam/modules/pam_krb5/Makefile

79

As part of release building, for one thing. It's part of the textproc/pod2mdoc port.

I don't think we should be building the base system differently based on which ports people have installed...

[ivy]

lib/libpam/modules/pam_krb5/Makefile

79

if this is from a port, it should be part of the vendor import process, not something run from a Makefile.

[cy]

lib/libpam/modules/pam_krb5/Makefile

79

+1

[des]

lib/libpam/modules/pam_krb5/Makefile

79

This is mostly just to document how the manual page was generated (and should be regenerated on update). The exists test can never be true since it only searches .PATH, not ${PATH}. I can replace it with .if !exists(pam-krb5.8) if you like, that way it's only rebuilt if you manually delete it.

[cperciva]

lib/libpam/modules/pam_krb5/Makefile

79

I would prefer .ifdef(I_AM_DOING_A_VENDOR_IMPORT) or something like that to make the purpose clear. This already confused three of us. :-)

[des]

rf

[cperciva]

LGTM