Turns out boostbook isn't usable with the present setup, for several reasons: 1) Boost.Build looks for a boostbook/xsl subdir, not a boostbook/styleshhet one. 2) By default, Boost.Build looks for boost-build../../tools/boostbook. This is hardly feasible with boost-build at /usr/share/boost-build (and wouldn't even really work with Boost.Build at /usr/share/boost/boost-build or whatever). By using
import boostbook-config ; in site-config.jam (or user-config.jam), a file that is part of Boost- Build, it is possible to put boostbook into /usr/share/boostbook/, as this location will then be queried for it (see line 60 of /usr/share /boost-build/tools/boostbook-config.jam). Similar files also exist for quickbook, xsltproc, and doxygen (the latter deprecated); thus, adding import xsltproc-config ; using doxygen ; import quickbook-config ; to site-config.jam (or user-config.jam, again) auto-configures quickbook, too. If Boostbook really needs to go to another location (such as /usr/share/xml/boostbook), line 60 of boostbook-config.jam would have to be modified in order to fit into this approach. Note that Boostbook requires Boost.Build! --- The revised version of the patch therefore adds recommendation for boost-build >= 2 and changes the Boostbook location to /usr/share/boostbook. It does not yet, however, touch any site- config.jam or user-config.jam file. This is partly because of their redundancy: the present boost-build package (2.0-m12-1) installs (identical) user-config.jam files both to /etc and to /usr/share/boost-build (and am empty site-config.jam). In Debian's 2.0-m12-2, this is fixed by not installing /usr/share/boost-build/user-config.jam anymore (and instead providing a non-empty /etc/site-config.jam). I've filed a bug report requesting syncing that version from debian: https://bugs.launchpad.net/ubuntu/+source/boost-build/+bug/271699 ** Attachment added: "tools.patch v2" http://launchpadlibrarian.net/17717388/tools.patch -- [needs-packaging] quickbook (boost) https://bugs.launchpad.net/bugs/239670 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs