On Wed, Jan 11, 2017 at 12:05 PM, Louis Dionne wrote:

...

the current docs for Hana are still broken: http://www.boost.org/doc/libs/1_63_0/libs/hana/doc/html/index.html yields "404 Not Found".

Thanks for reporting this. Rene, has there been a change in the way documentation is generated for releases? You made this commit [1] to Hana a while ago, which suggests that something changed, but what?

What changed is that the automated doc build CI now uses one of those two targets *only* for building the docs of any library. If you want your docs built fresh for a release archive as *standalone* (ie not integrated) you need to define "boostrelease" to alias the target(s) that need to get built for the docs. If they are integrated into the global docs you would defined the "boostdoc" alias to the appropriate docbook target to build and include. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

Rene Rivera-2 wrote

On Wed, Jan 11, 2017 at 9:59 PM, Rene Rivera <

grafikrobot@

> wrote:

...

On Wed, Jan 11, 2017 at 12:05 PM, Louis Dionne <

ldionne.2@

>

...

wrote:

...

...

the current docs for Hana are still broken: http://www.boost.org/doc/libs/1_63_0/libs/hana/doc/html/index.html yields "404 Not Found".

Thanks for reporting this. Rene, has there been a change in the way documentation is generated for releases? You made this commit [1] to Hana a while ago, which suggests that something changed, but what?

What changed is that the automated doc build CI now uses one of those two targets *only* for building the docs of any library. If you want your docs built fresh for a release archive as *standalone* (ie not integrated) you need to define "boostrelease" to alias the target(s) that need to get built for the docs. If they are integrated into the global docs you would defined the "boostdoc" alias to the appropriate docbook target to build and include.

PS. It's my fault for not having the time after getting that working on the last release to adjust documentation to say that.

Okay, I've fixed it on develop [1] but for the time being is it possible to upload the documentation manually? It would be nice if Hana could have its documentation without waiting for the next release. Louis [1]: https://github.com/boostorg/hana/commit/7dfc94962b88a1532add7b3a6afb090b379b... -- View this message in context: http://boost.2283326.n4.nabble.com/docs-for-hana-broken-on-webpage-boost-1-6... Sent from the Boost - Dev mailing list archive at Nabble.com.

Daniel James-3 wrote

On 12 January 2017 at 07:38, Louis Dionne <

ldionne.2@

> wrote:

...

Okay, I've fixed it on develop [1] but for the time being is it possible to upload the documentation manually?

Missing documentation and fixes can be added to 'doc/fixes/boost_1_63_0' directory in the website repo, although I'm going to move the 'doc/fixes' directory to a separate repo soon as it's getting a bit too big.

What branch should I submit my PR against in the `website` repo? Thanks, Louis -- View this message in context: http://boost.2283326.n4.nabble.com/docs-for-hana-broken-on-webpage-boost-1-6... Sent from the Boost - Dev mailing list archive at Nabble.com.

On 17 January 2017 at 08:04, Oliver Kowalke wrote:

2017-01-12 9:15 GMT+01:00 Daniel James :

...

On 12 January 2017 at 07:38, Louis Dionne wrote:

...

Okay, I've fixed it on develop [1] but for the time being is it possible to upload the documentation manually?

Missing documentation and fixes can be added to 'doc/fixes/boost_1_63_0' directory in the website repo, although I'm going to move the 'doc/fixes' directory to a separate repo soon as it's getting a bit too big.

I can't find directory 'doc/fixes' in branch master or dev

I moved it into a separate repo, as I mentioned into the quote you're replying to. https://github.com/boostorg/documentation-fixes Although, I might rebuild it to have the full history from the website repo, But the best way to deal with this would be to fix the documentation build, and then I could copy the correct documentation from there. Did you try the change I suggested?