Re: Build-depends method

[Sven Luther <sven.luther@wanadoo.fr>]

On Sun, Jan 25, 2004 at 10:13:21PM +0100, Steinar H. Gunderson wrote:
> On Sun, Jan 25, 2004 at 11:29:07AM -0800, Shaun Jackman wrote:
> > When packaging a new package, what's a methodical way to find *all* 
> > its Build-Depends packages?
> 
> I was surprised nobody brought this pearl from the maint-guide up yet:
> 
>   strace -f -o /tmp/log ./configure
>   # or make instead of ./configure, if the package doesn't use autoconf
>   for x in `dpkg -S $(grep open /tmp/log|perl -pe 's!.*open\(\"([^\"]*).*!$1!' |grep "^/"| sort | uniq| grep -v "^\(/tmp\|/dev\|/proc\)" ) 2>/dev/null|cut -f1 -d":"| sort | uniq`; do echo -n "$x (>=" `dpkg -s $x|grep ^Version|cut -f2 -d":"` "), "; done

Will this not catch also the programs that are probed but maybe not used
or something ? An example is forexample a packages whose configure
probes for either bison or yacc, but you need only one in the
build-dependencies, or maybe not, since i guess this is build-essential
or something.

Maybe it would be better to check the actual build, not the configure
process, and have some posttreatment which will explore the dependency
tree and find the smallest subset thereof.

Friendly,

Sven Luther