finding out about (system) dependencies

[Matthias Klose]

A whole bunch of system libraries are tried to load using dlopen, instead of
linking against these libraries. Is this a leftover windowism, or expected
behaviour? It makes it somewhat difficult to automatically add runtime
dependencies for the runtime packages.

Scanning the strings output from the library packages, the following libraries
seem to be dlopen'ed:

LIB: libawt.so: libXm.so.3
LIB: libfontmanager.so: libfreetype.so.6 libjpeg.so
LIB: libnet.so libgconf-2.so libgconf-2.so.4
LIB: headless/libmawt.so: libfontconfig.so.1 libfontconfig.so
	 libcups.so.2 libcups.so
LIB: xawt/libmawt.so: libsunwjdga.so libXrandr.so.2
	libgnomevfs-2.so.0 libgnome-2.so.0 libfontconfig.so.1
	libfontconfig.so libGL.so.1 libcups.so.2 libcups.so
	libgtk-x11-2.0.so.0

running debian's dpkg-shlibdeps only identifies as dependencies:
libc6, libfreetype6, libgcc1, libx11-6, libxext6, libxi6, libxtst6

so I assume these dependencies have to be managed manually as long as the
libraries are not linked against the system libraries?

  Matthias