Re: [boost] Test build for 1.56 available

Subject: Re: [boost] Test build for 1.56 available
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-07-08 09:04:14

On Tuesday 08 July 2014 13:10:19 Paul A. Bristow wrote:
> > -----Original Message-----
> > From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Antony
> 
> Polukhin
> 
> > Sent: 08 July 2014 10:27
> > To: boost_at_[hidden] List
> > Subject: Re: [boost] Test build for 1.56 available
> > 
> > 2014-07-08 12:44 GMT+04:00 Andrey Semashev <andrey.semashev_at_[hidden]>:
> > > On Tuesday 08 July 2014 09:58:11 Oliver Kowalke wrote:
> > > > 2014-07-08 9:53 GMT+02:00 Antony Polukhin <antoshkka_at_[hidden]>:
> > > > > Links to the docs are broken for the following libraries in
> > > > > libs/libraries.htm: Algorithm, Align, CompressedPair, Context,
> > > > > Core, Coroutine, EnableIf, Functional/factory, Functional/forward
> > > > > Log,
> > > 
> > > Odeint,
> > > 
> > > > > Phoenix, Range, Spirit, Swap, TTI, TypeIndex, Units
> > > > 
> > > > does this issue require action on the side of the library authors
> > > > (like generating and check-in of html etc.)?
> > > 
> > > No autogenerated files in git, please. I believe these test archives
> > > simply don't include all docs (not sure if that was intentional).
> > 
> > Looks more like missing redirects or infinite loop of redirects.
> > 
> > Andrey is absolutely right about autogenerated files in git. About a half
> > of
> the
> 
> > archive is consumed by the autogenerated docs.
> > 
> > It would be good to have "./b2 docs" in next release and remove all the
> 
> generated
> 
> > docs from git.
> 
> I agree - I've found that any generated items in git make maintenance
> disastrously messy.
> 
> But we also need to ensure that the setup of the tools, Quickbook, Autoindex
> and Inspect are all automatically built to a 'standard' location, and in
> the users path, so that the
> 
> ./b2 docs works slickly for everyone.
> 
> It will of course take quite a long time - hours ? - to regenerate all the
> docs
> :-(

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.