Logcheck dependency hell

[n j]

Hello,

could anyone help me what command should I use to find out which
logcheck-required port _exactly_ is trying to install half of the X
libraries?

The logcheck port lists the following build depends (output of
pretty-print-build-depends-list):

This port requires package(s) "compositeproto-0.4 damageproto-1.1.0_2
dmxproto-2.2.2 docbook-1.4 docbook-4.1_3 docbook-4.2 docbook-4.3
docbook-4.4 docbook-4.5 docbook-5.0_1 docbook-sk-4.1.2_4
docbook-to-man-1.0_1 docbook-xml-4.2_1 docbook-xml-4.3 docbook-xml-4.4
docbook-xml-4.5 e2fsprogs-libuuid-1.41.4_1 expat-2.0.1 fixesproto-4.0
fontcacheproto-0.1.2 fontconfig-2.6.0,1 fontsproto-2.0.2
freetype2-2.3.7 inputproto-1.5.0 iso8879-1986_2 jade-1.2.1_9
kbproto-1.0.3 libFS-1.0.1 libICE-1.0.4_1,1 libSM-1.1.0,1
libX11-1.1.99.2,1 libXScrnSaver-1.1.3 libXTrap-1.0.0 libXau-1.0.4
libXaw-1.0.5_1,1 libXcomposite-0.4.0,1 libXcursor-1.1.9_1
libXdamage-1.1.1 libXdmcp-1.0.2_1 libXevie-1.0.2 libXext-1.0.5,1
libXfixes-4.0.3_1 libXfont-1.3.4,1 libXfontcache-1.0.4 libXft-2.1.13
libXi-1.2.0,1 libXinerama-1.0.3,1 libXmu-1.0.4,1 libXp-1.0.0,1
libXpm-3.5.7 libXrandr-1.2.3 libXrender-0.9.4_1 libXres-1.0.3_3
libXt-1.0.5_1 libXtst-1.0.3_1 libXv-1.0.4,1 libXvMC-1.0.4_1
libXxf86dga-1.0.2 libXxf86misc-1.0.1 libXxf86vm-1.0.2 libdmx-1.0.2_1
libfontenc-1.0.4 liboldX-1.0.1 libpthread-stubs-0.1 libxcb-1.1.93
libxkbfile-1.0.5 libxkbui-1.0.2_1 perl-5.8.9 pixman-0.13.2
pkg-config-0.23_1 printproto-1.0.4 python25-2.5.2_3 randrproto-1.2.1
recordproto-1.13.2 renderproto-0.9.3 scrnsaverproto-1.1.0
trapproto-3.4.3 videoproto-2.2.2 xcb-proto-1.3 xextproto-7.0.5
xf86dgaproto-2.0.3 xf86miscproto-0.9.2 xf86vidmodeproto-2.2.2
xineramaproto-1.1.2 xmlcatmgr-2.2 xmlcharent-0.3_2 xorg-libraries-7.4
xproto-7.0.14 xtrans-1.2.3" to build.

However, I really doubt that something as simple as logcheck really
needs all of these dependencies and I can't trace it far enough to see
which dependency is pulling all these X libs. How can I trace this
dependency hell? Is logcheck really this "heavy" or is the port that
bad?

Thanks for any input,
-- 
Nino