To strict dependencies when building package

[Kjetil Thuen <Kjetil.Thuen@student.uib.no>]

I am just about to release a new version of a program I am writing. For
this version I have promised my users binary packages.

Making the .deb went relatively smoothly, but the resulting packages
dependencies turned out to strict. The package is built on a machine
with Helix-GNOME installed (and the app uses the GNOME libs), and the
dependencies turned out like this:

Depends: gdk-imlib1 (>= 1.9.8.1-helix1), libart2 (>= 1.2.3-helix2), libaudiofile0, libc6 (>= 2.1), libc6 (>= 2.1.2), libdb2 (>= 1:2.4.14-7), libesd0 (>= 0.2.16) | libesd-alsa0 (>= 0.2.16), libgdk-pixbuf2, libglib1.2 (>= 1.2.0), libgnome32 (>= 1.2.3-helix2), libgnomesupport0 (>= 1.2.3-helix2), libgnomeui32 (>= 1.2.3-helix2), libgtk1.2 (>= 1.2.8-helix1), libjpeg62, libpng2, libtiff3g, libz1, xlib6g (>= 3.3.6)

Others have succesfully tried force installing the package on Debian
boxes with the GNOME from potato.

So - I know for a fact that the compiled program will work with older
gtk and gnomelibs. How can I make the package reflect this? Manually
typing the dependencies into the Depends field in the control file seems
very kludgy.

Kjetil Thuen
-- 
    Quidquid latine dictum sit, altum viditur
PGP: http://grustibus.sourceforge.net/kjetilt-pgp.asc