Okay just to track this down better, I'm going to attach the last draft I've prepared for pam eclass. The eclass is though for handle pamd files and pam modules: - the firsts are installed in /etc/pam.d by the newpamd and dopamd functions, which installs them just if pam useflag is set and is in $IUSE (this fixes for exampel bug #86823) - the seconds are installed in the correct directory for pam modules which depends on the pam implementation installed: for sys-libs/pam (Linux-PAM) they installs in /$(get_libdir)/security/, for sys-libs/openpam (just in g/fbsd overlay for now) they are installed in /usr/$(get_libdir) (that's just a temporary solution actually but for now I don't want to mess too much with openpam to add support for loading them from a specified path). There's also a new function, pamd_mimic_system which is used to just include system-auth configuration file for the given access levels. This allows to avoid using pamd files in $FILESDIR for packages which just mimics system-auth. HTH, Diego
Created attachment 59246 [details] pam.eclass
Created attachment 59286 [details] pam.eclass Updated eclass with /etc/security/* support (needed to cleanup gdm support).
pam eclass is now in tree :) This means that blocked bugs are now un-blocked.
