Re: Build-depends method
Scripsit Shaun Jackman <sjackman@telus.net>
> When packaging a new package, what's a methodical way to find *all*
> its Build-Depends packages?
One fairly effective method is to try to build in a chroot (see
pbuilder etc) with only build-essential packages installed initially.
It's not entirely foolproof because the package may depend on directly
on a-dev and b-dev, but if a-dev currently depends on b-dev you might
miss the explicit build-dependency, which can cause FTBFS's if a-dev
later stops depending on b-dev.
It's also a good idea to check the ldd output from the chroot-built
package against the output from one build in one's usual environment.
If there's a difference, the upstream source's configure script is
probably doing some autodetection of available libraries, and you need
to figure out which ones you want the Debian package to include, and
explicitly tune out the rest with --without-foo arguments to configure.
--
Henning Makholm "Det er jo svært at vide noget når man ikke ved det, ikke?"
Reply to: