Package: dpkg-dev Version: 1.10.9 Severity: wishlist Hi,
To my mind dpkg-buildpackage should try to minimize build dependancies when it is possible. I see 2 levels for this improvement. 1) dpkg-buildpackage should warn the user if a dependency appear more than once in Build-Depends. For example if libadns1-dev is a dependency, and if it is listed more than once in Build-Depends (with differents version for exemple), dpkg-buildpackage should warn the user. 2) dpkg-buildpackage should warn the user if a dependency is a dependancy from an other package listed in Build-Depends. For example if libadns1-dev is a dependency, and if libadns1 is listed in Build-Depends, dpkg-buildpackage should warn the user. Or If A is a primary dependency and B a dependency of A, C a dependency of B and so on. A->B->C->D ... If A and C (and/or D, E ...) are listed in Build-Depends, dpkg-buildpackage should warn the user, because C (and/or D, E ... ) should not be there. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux quirinus 2.4.20 #1 Son Apr 14 09:53:28 CEST 2002 i686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] Versions of packages dpkg-dev depends on: ii binutils 2.13.90.0.18-1.3 The GNU assembler, linker and bina ii cpio 2.5-1 GNU cpio -- a program to manage ar ii make 3.80-1 The GNU version of the "make" util ii patch 2.5.4-11 Apply a diff file to an original ii perl [perl5] 5.8.0-17 Larry Wall's Practical Extraction ii perl-modules 5.8.0-17 Core Perl modules. -- no debconf information
