Users are sometimes confused about what Boost.Build does and why, and what's Jamfile, anyway. We can do this:

Jamfiles of all project should start with comment saying this is Boost.Build file, and giving link to the list of rules to be used in Jamfile and jam syntax.

We probably can have a version of --debug-building that is less verbose and more user-oriented:

building exe:foo/bar with debug/threading=multi

installing foo:....

Maybe, for C++ Boost it would be valuable to list libraries that will be built in even more apparent format:

Boost version 1.35.0
 
  Configuration:
 
    bjam command......: bjam --prefix=/usr/local -stdlib=stlport --with-thread --with-circular_buffer
    prefix............: /usr/local
    debug.............: yes
    stdlib............: stlport     <-- or standard if stlport is not used
 
  Libraries:
 
    circular buffer...: yes
    filesystem........: no
      .
      .
      .
    python............: no
    test..............: no
    thread............: yes