Comment 14 for bug 638596

Chris, no need to clarify. Also the rules didn't suddenly change. Perl modules
are a corner case where the normal rules of dependency extraction wrt
executable bits don't apply, never have (perl modules generally aren't supposed
to be executable so that can't be used for detection). The current "file"
utility (whose library rpmbuild internally uses for classifying files) just
seems to be far more eager at claiming files to be "perl modules" than the
older versions, that's where the change in behavior comes from in this and the
other related bugs.

Like I said, extracting dependencies for documentation doesn't make sense to me
either. But the rpmbuild file classifier is built with the assumption that it
can figure out everything from the files on disk, it doesn't "see" what is
specified as %doc etc in the spec. I'm just looking at how to best fix this,
hopefully eliminating bunch of other related hacks in the process instead of
adding new ones. If that starts looking like more of a long-term thing, we can
always just drop in another hardcoded hack such as the "fix" in comment #12 to exclude the docdir where necessary.