buildbot taking some strange steps

[Jeff Johnson]

Just so these are recorded...

===

In the build-sdk build, we see these in the list of steps:

2. clear-old-packaging 'rm -rf ...' ( 0 secs )
3. checkout-packaging 'bzr checkout ...' ( 10 secs )
4. reset-sdk 'reset-sdk' ( 19 secs )

However, packaging is not used, so steps 2 and 3 are not needed; and the sdk
build is self-contained (builds itself with native compiler, and uses result to
build the target which is packaged) so there is no need to install any
particular SDK version in order to proceed with the build.

All three steps could/should be dropped.

===

In the appbat build, if the configure step fails, processing should not
proceed. Here's such a run:

21. configure './configure' failed ( 9 secs )
22. check-pkgcache 'extras/entitycheck.py -c ...' failed ( 0 secs )
23. build-appbat 'make appbat ...' failed ( 0 secs )
24. build-desktop 'make desktop ...' failed ( 0 secs )
25. build-addons 'make addons ...' failed ( 0 secs )
26. check-appbat 'make check-appbat' failed ( 0 secs )
27. check-desktop 'make check-desktop' failed ( 0 secs )
28. check-addons 'make check-addons' failed ( 0 secs )

In this case steps 22-28 (and beyond) aren't worth proceeding with after the
configure step has failed.