On Thu, 10 Mar 2011 13:32:27 -0800 Steve Langasek <vor...@debian.org> wrote:
> FWIW, mk-build-deps is close, but not exactly what I'm looking for > personally. I really want a command that, without needing to specify any > extra options, does 'mk-build-deps -i -r debian/control', because I think > this is the common case. I also think we're missing as a standard interface > a tool that *tells* us what build-dependencies need to be installed (and > what build-conflicts need to be removed), in a form that's automatically > consumable by other tools including, but not limited to, apt-get. > dpkg-checkbuilddeps fails this because it only tells which b-d's are > unsatisfied, in a form that has to be further processed. http://www.linux.codehelp.co.uk/serendipity/index.php?/archives/222-Checking-build-dependencies.html > I think a standard tool to handle this "what do I need to install and remove > to satisfy the build-depends for the current package" question would be > useful at a lower level than devscripts, fwiw. :-) embuilddeps has a -n|--dry-run option which does exactly that. I'm open to it being renamed and/or put into another package - it is perl and uses libdpkg-perl. I'd welcome comments on what it cannot still do and if it gets things wrong for particular source packages. It also has explicit support to act as the dependency-resolver inside pbuilder (native and cross) and Hector & I are looking at how it can be used inside sbuild too (native and cross). -- Neil Williams ============= http://www.linux.codehelp.co.uk/
pgpnxPqxMvPZy.pgp
Description: PGP signature
