On 9/07/2014 01:04, Andrey Semashev wrote:
Personally, I think distributing pre-built docs as a separate package is a better option. Building docs locally require toolchain that is not distributed or built with Boost, so offering users to build the docs themselves is not quite practical. At the same time, I'm sure most users won't use bre-built docs and just go online, so packaging docs with the sources seems like a waste.
+1. As a user I've always just looked at the online docs, so having them in the download is just a waste of space. But I expect that many users will want to have offline docs, so making it a separate package is the best of both worlds. (Ideally, when modular boost really kicks off, each library should have a separate docs package so that the auto-library-downloading-tool can install only those docs that are actually required for the library subset in use.)