Comment 6 for bug 345137

I have a hard time believing that using NIS without also knowing about the existence of nscd is a common scenario at all. NIS itself is an unlikely technology to be deploying, and I would indeed expect the deployment to involve one or more experts who would be familiar with nscd. Which is not to say that I think that these experts would automatically choose to *install* nscd; my experience is that it is not at all a reliable technology, and even when using nss_ldap (which is a more expensive network operation than nis lookups) I have avoided deploying nscd whenever other options were available (such as local caching LDAP servers).

Adding it as a Suggests: is certainly fine with me; as I said, it's consistent with what other packages are doing.

BTW, the nis package is also the package providing the nis server. Pulling nscd in by default (as would happen with Recommends:) could cause NSS lookups to *slow down* on the server...