Re: [boost] [range] Should html docs be checked in?

Subject: Re: [boost] [range] Should html docs be checked in?
From: Mostafa (mostafa_working_away_at_[hidden])
Date: 2013-12-28 15:21:54

On Sat, 28 Dec 2013 07:08:44 -0800, Daniel James <daniel_at_[hidden]>  
wrote:

> On 28 December 2013 11:16, Neil Groves <neil_at_[hidden]> wrote:
>>
>> I have been generating the html and checking it in. However if there is  
>> a
>> way to transition to a better system I am all for it.
>
> I run an occasional documentation build (once or twice a week) which
> is added to the final release. The documentation from the master
> branch is also uploaded to sourceforge, but I'm thinking of changing
> it so that it's uploaded to the website. I can add range to the build.

Speaking of documentation and the final release, every time I have to  
build boost from scratch I have to scrounge third party distros for boost  
documentation (like Ubuntu or Fedora), because it seems that there is no  
way to centralize and install the docs. If you're already building and  
adding docs to the final release, can you also add an optional install  
hook so that they may all install in one location (like share/doc/).

Thanks,

Mostafa