bjam has no symlink, but only the versioned binary, like bjam-1_42. if it is used somewhere there is no clean way to create an ebuild with bjam. please create a boost-build eselect module, which manages the /usr/bin/bjam symlink, thanks!
Ebuilds should not rely on boost or bjam symlinks but always use the latest supported version of boost-build or boost. Look at dev-cpp/xsd for an example on how to properly depend on/use boost.
additional explanation for this: otherwise the package manager will never be able to track correct slot dependencies (which gets important with the next EAPI release).
