Jonathan Nieder <jrnie...@gmail.com> wrote: > Do I understand correctly that in the stage-N build, the installed > versions of all build-time dependencies (and their dependencies, et > cetera) must have build-stage >= (N-1)? What about the standard > build? Does it happen repeatedly, incrementing the stage number, > until the result is stable, or is there some other method for > approximating the limit? :)
Good question. No formal requirements have been specified along these lines, and I don't think that they are needed, except to say that an uploadable build should always be done against complete build-deps - anything built against 'staged' packages must be considered 'tainted'. So if we have A B-D: C-bin1 B B-D: A-bin1 C B-D: A-bin1,B-bin1 We untangle this by building A-stage1, B(tainted), C(tainted), A, B, C Some code to note the tainting at build-time and mark the built package accordingly would mean that nothing external needs to track this state. I'm not sure how easy that is to do. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
