2011/10/7 Bernhard R. Link <brl...@debian.org>: > * Дмитрий Матросов <sgf....@gmail.com> [111007 16:27]: >> But in the section 7.7 of Debian policy manual: >> > clean, build-arch, and binary-arch >> > Only the Build-Depends and Build-Conflicts fields must be satisfied when >> > these targets are invoked. >> > build, build-indep, binary, and binary-indep >> > The Build-Depends, Build-Conflicts, Build-Depends-Indep, and >> > Build-Conflicts-Indep fields must be satisfied when these targets are >> > invoked. >> >> And footnote 55: >> > Anyone building the build-indep and binary-indep targets is assumed to be >> > building the whole package, and therefore installation of all build >> > dependencies is required. >> >> So, as i understand, in this case dependencies will look like >> >> binary : binary-arch binary-indep >> binary-indep : build-indep build-arch <----? > > What you write here looks like makefile dependencies, i.e. like > something written in debian/rules. In that sense it is obviously > wrong. Nothing says you must have called build-arch to be able > to run build-indep or binary-indep. > > All it says is that people are not required to add things to > "Build-Depends-Indep:" which are already in "Build-Depends:".
So, this means that there is no strict relationship between content of Build-Depends-* field and build-* target dependencies like: "'Build-Depends' field contains all dependencies for 'build-arch' target and nothing more", or "'Build-Depends-Indep' contains all dependencies for 'build-indep' target and nothing more". Am i understand you correctly? > P.S: Note that currently Build-Depends-Indep is not working as > Debian is stalled in a decade old dream for a technical solution, > so one has to put everything in Build-Depends anyway... Well, i just want to understand theory :) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cafdvufm4rhnwdt9--zydsl09ktqkfoskzxit38kc9_ucwn_...@mail.gmail.com
