Bastian> Your suggestion splitting out and removing after one
Bastian> release would be fine for me.
Helmut, I was hoping for a sanity check.
Bastian wants to split out some code from pam.
He wants to move pam_userdb.so into its own package to remove db5.3 from
the pseudo-essential set.
I've said that I'd be fine with that if we had libpam-modules depend on
the new package for a release. (It might be okay to do something else,
but that would require surveying users or detecting breakage in ways
that require more thought than I would like to spend).
Complications:
* pam is ppseudo-essential
* usrmerge transition (pam libdir is currently /lib)
So ignoring essential and usrmerge, I think the new package would
replace/breaks libpam-modules << the split point.
Do you have advice on what we want to do given usrmerge and essential?
--Sam
