Re: Correctly determining Build-Depends
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Maykel Moya wrote:
| I'd followed the step recommended in maint-guide to obtain Build-Depends
|
| $ objdump -p /usr/bin/foo | grep NEEDED
|
I use another form, I look in compiling time the "touched" packages, I
use this script:
# Here's a hack you can use to find out which packages your package
needs to be built:
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
It work quite nice.
| then a dpkg -S on each founded library. But I have now a (not so little)
| list of packages. I can add all of their -dev versions to Build-Depends
| but there are already dependencies among then.
|
| Do exists a tool to automatize this task, I mean, obtain the minor
| subset of packages that resolved (which their respective dependencies)
| to a given a list of packages.
|
| Regards
| mike
|
|
|
- --
email: Miguel Gea Milvaques <debian(arroba)miguelgea.com>
Blog : http://www.livejournal.com/users/xerakko/
Web : http://www.miguelgea.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCBkliNTNQylgICMQRAsPyAJ9gKK9FEDEHEG76y7HTARDpyED1/ACgza1m
XlJyEQy8fq39lefJeCm+zE0=
=qXfw
-----END PGP SIGNATURE-----
Reply to: