> Because most PAM problems in ports are bugs in the ports themselves, > which Linux-PAM just happens to tolerate and OpenPAM doesn't. In > other words, it should be possible to find a solution to the problem > which works equally well for Linux-PAM and OpenPAM, without the need > to know which is which. And as a last resort, you can make OpenPAM- > specific code conditional on the _OPENPAM preprocessor symbol.
No difference for port's user how source is change. Either a patch will apply for 5.0 only when port build or general pach where PAM version detects with preprocessor directives. Result code will be the same. I think it's a style question. What the community opinion? > > What fix will be a right one? > > I can't tell you unless you show me what you believe needs fixing. What a right way escape from PAM_CONV_AGAIN/PAM_TRY_AGAIN and relate code from LINUX_PAM? ---- Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
