[Please don't CC me] * Sam Hartman <hartm...@debian.org> [250115 14:45]: > Do you actually have a system on which you want these man pages and on > which the extra space of libpam-doc would be a problem?
No. > Unless there's a compelling need, my answer is that I don't understand > why manpages should be separated from other documentation in this instance. I have a strong aversion to the mantras "disk space is cheap", "memory is cheap", "network bandwidth is cheap", or any other denigration of seemingly abundant resources. They are the enemy of good programming principles. In this particular case, I don't think putting the man pages in with the other docs is a problem. But if every package did this, the bloat would be significant. I think it sets a bad precedent. My original message was really responding to: * Sam Hartman <hartm...@debian.org> [250115 11:44]: > I'm not actually convinced that normal Debian users need man pages for > all the pam modules on all Debian systems, and a suggests relationship > should be sufficient. I think you underestimate the amount these man pages are used and their value. The suggestion to create a new libpam-manpages was really just one way to keep the status quo without bringing in the additional doc'n. With a Recommends relationship, it would allow installing libpam-modules without the man pages, if desired, but would include them by default (except where the user had opted out of installing Recommends by default). I am fine with putting the man pages in with libpam-modules-bin. ...Marvin
