Right now, pambase does install a set of static /etc/pam.d files based on USEflags passed. This is getting more and more inconvenient, considering the growing number of optional modules added. I'd suggest installing smaller modules in the ebuild, and using a mechanism similar to env-update, or even an eselect module, to generate the actual modules based on user preferences without rebuilding pambase.
No, already thought about it but unless _you_ come up with a full design this just won't happen.
(In reply to comment #1) > No, already thought about it but unless _you_ come up with a full design this > just won't happen. Could you explain a little more? Does this mean I have to provide a spec with explanation on how to achieve this, or a spec good enough to overcome some difficulties which you come up with earlier?
