[EMAIL PROTECTED] (Colin Watson) writes:
> >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 de
Kjetil Thuen <[EMAIL PROTECTED]> 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
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
3 matches
Mail list logo
