Hi,
I suggest to start a formal procedure of deprecating modules.
For example, we could use a simple 3-step deprecation algorithm:
- declare a module as deprecated in the upcoming release N,
- do not build it by default right after release N,
- remove it from the tree right after release N+1.
I suggest starting with pam_tally (obsoleted by in-tree pam_tally2),
pam_tally2 (obsoleted by out-of-tree pam_faillock), and pam_cracklib
(obsoleted by out-of-tree pam_passwdqc and pam_pwquality), this means
declaring them as deprecated in 1.4.0 release.
This would mean making Linux-PAM releases more regular and more often,
e.g. twice a year.
Comments?
--
ldv