On Sun, May 20, 2007 at 12:56:04AM +0200, Jörg Sommer wrote: > thanks for your report. Maybe, you can help me with this bug or should I > ask on d-mentors/d-devel?
I think Norbert's follow-up explains this pretty accurately. > ** Using build dependencies supplied by package: > Build-Depends: debhelper (>= 5), dpatch, autotools-dev, flex, clisp-dev > Build-Depends-Indep: texlive-latex-base, texlive-lang-cyrillic, > texlive-latex-recommended, cm-super > Checking for already installed source dependencies... > debhelper: already installed (5.0.49 >= 5 is satisfied) > dpatch: missing > autotools-dev: missing > flex: missing > clisp-dev: missing > Checking for source dependency conflicts... > So, it installs only the packages from Build-Depends, but later it calls > debian/rules build > The Debian policy says in section 7.6. > The dependencies and conflicts they define must be satisfied (as > defined earlier for binary packages) in order to invoke the targets in > `debian/rules', as follows:[1] > `Build-Depends-Indep', `Build-Conflicts-Indep' > The `Build-Depends-Indep' and `Build-Conflicts-Indep' fields must > be satisfied when any of the following targets is invoked: > `build', `build-indep', `binary' and `binary-indep'. > ^^^^^ > So, why the build target is called even though the dependencies from > Build-Depends-Indep aren't satisfied? Policy's language simply doesn't agree with the buildd implementation it was originally intended to document. Transitioning to the use of "build-arch" on the buildds has issues that have been discussed extensively on the lists, because build-arch is currently not a required target. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
