build scripts again

Hello! Last week I tried out TDE building scripts: for example 99_build_TDE.sh which successfully finished its work in 38 hours. But later that week I looked into 0_logs/build_result.log and found there some "[FAILED]" messages for ten packages ("k3b-i18n", "k9copy", "kaffeine", "kasablanca", "katapult", "kbarcode", "kbfx", "kbibtex", "kbiff", "kpilot"). Later I tried to run the same script in "local mode" ("-l" flag in BUILD_DEFAULT_OPTIONS variable of _config.sh) but it seems the modules don't see the compilation results of the previously compiled modules. And I didn't find any way in the scripts for them to see. So here are some questions about building scripts: 0) Do I understand correctly that "modules" (as this word is used in command "build_module" for example in 06_applications_03.sh script) are corresponding 1-to-1 to debian source packages on the one hand and to git submodules of TDE/tde repository on the other hand? 1) What exactly is the mechanism used while building with "pbuilder" (i.e. WITHOUT "-l") for the module A to use package B built in one of the previous modules? 2) Does something similar exist while building everything in "local mode" (i.e. WITH "-l") on a clean machine? I see there only the *.deb files, but they don't seem to be installed immediately after creation and then the next step is about to start already and *.deb files are just left there not installed. 3) Is there any simple way to disable colored output which is very nice on the terminal, but quite disturbing while reading logs in a file? 4) Is there a way to stop let's say 99_build_TDE.sh script if a single module compilation failed? 5) Sometimes I see the following lines in the log file (using "show log" -sl option and piping output into a file): dpkg-checkbuilddeps: error: Unmet build dependencies: tdelibs14-trinity-dev [and many more -I.D.] dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) Building completed SUCCESSFULLY [in green color -I.D.] Does this combination (package can't be built, but it's kinda success nevertheless) have any sense or is it some kind of error in the scripts? The meaning of all these questions for me is to understand how to create an environment, where I can rebuild the whole TDE in a reliable way (run a single command and be sure that its success indicates nothing went wrong and everything is built) on a clean machine. Thanks! -- Ilya D.