You're right, it is in PBP, in the section on Documentation Boilerplates - I'd forgotten about that. The specific bit about the DEPENDENCIES section is on page 135. Surprisingly there doesn't seem to be a Pod::Weaver / Dist::Zilla plugin to generate this.
PBP doesn't mention it, but you might also want to draw a distinction between what deps are needed to install / test, and which ones are used by the dist vs by the module. For single-module dists that's straightforward, but not for more complicated dists.
Not sure what I think about this section. It's useful for someone looking at your module, but you need to present the right information in an easy-to-grok way. And it needs to be maintained. And it duplicates information presented by MetaCPAN for example, which is derived from metadata. Hmm.
]]>For example, we could have an x_similar_to, or something like this, which is for listing modules which provide at least some of the same functionality. This would enable a [more like this] function in MetaCPAN, for example.
Then we could also have x_superseded_by, x_deprecated (discussed elsewhere as well, I know)
Would be even better if it had some more ontological juice, but I don't think enough dists would get that to make it worth while.
We're drifting into the tagging discussion, and things like Yanick's suggestion: http://techblog.babyl.ca/entry/metacpan-recommendations
]]>