Re: To strict dependencies when building package

[cjw44@flatline.org.uk (Colin Watson)]

Kjetil Thuen <Kjetil.Thuen@student.uib.no> wrote:
>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.

Short of building your packages inside a stock potato chroot, you might
try using a debian/shlibs.local file in your package. Section 12.2 of
the packaging manual has all the details on how you should go about
this.

-- 
Colin Watson                                     [cjw44@flatline.org.uk]