Plan0)

 - FAILURE -- failed stage, # of recursive brokenness
 - succeeds -- a number of packages to build

 - checks: internal compiler error

 - Run pkg_info once for pkg_summary and pkg_enriched_summary

 - save options like -a and -l to META/tmp/somewhere
   and restore it when -r

 - compare with previous branch results

 - Ensure that dependencies activated using bl3 PROVIDEs something
   REQUIRED by the package.

 - Explicitely set SU_CMD to something noisy.

 - Analyser:
   - 'make checksum' failures
   - "Gray" text if no warnings
   - unnecessary CONFLICTS
   - possibility of installation each package in the repository
   - config.log may help to recognize bad DEPENDS and BUILD_DEPENDS
   - recognize previous bulk build and packages failed at that time
     which succeeded in new bulk build. Compare {BUILD_,}DEPENDS then

 - Update README!!!

 - pkg_info -N

 - use shlock for protection against running several instances of distbb

 - distbb.1

 - META/packages_status.txt

 - Automatically create r/o chroot under NetBSD, replacement for pkg_comp.

Plan1)

 - links to package's configure.log(s) from PKGNAME/stage_*.html?

 - rebuilding packages changed in CVS (without version changes)?

ANY IDEAS? LET ME KNOW. VLE@GMX.NET
