[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: pbuilder and ${shlibs:Depends}

On Fri, 18 Mar 2011, Panayiotis Karabassis wrote:
> I am still a little confused about this. Could you provide an
> example/documentation to clarify this? From experience, I believe that
> it WILL expand to LIBRARIES (not executables) that the program needs to
> run, if said libraries are installed at build time. If not, what's its
> purpose?

It will expand to libraries which are listed in the NEEDED section of the
ELF binaries present in your package.

> > Add the missing dependencies manually AND use the variable. (At least
> > this is what I do in all my packages.
> Thank you very much! This is really all I needed to know.

Unfortunately this is wrong, at least for ELF binaries. Usually if you
don't have all the dependencies that you expect, it's because they are
optional and are disabled when they are not found during ./configure.

Thus the correct solution is to add the required -dev packages in the
Build-Depends so that ./configure finds the optional libraries that you
want your program to use.

Adding manual dependencies on C libraries is almost always wrong.

> BTW, I'm not actually using dpkg-shlibdeps, but rather jh_depends. I
> wanted to save some complication, since most developers are probably
> more familiar with the former.

You did not save some complication you just got wrong information due to
this.  It's unlikely that jh_depends works like dpkg-shlibdeps.

I guess you need to have all the jars installed at build time and thus you
want to add them to Build-Depends. But you should really ask for
confirmation someone on debian-java@ or an experienced java packager (or
maybe it's in jh_depends documentation).

Raphaël Hertzog ◈ Debian Developer

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
                      ▶ http://RaphaelHertzog.fr (Français)

Reply to: