Boost C++ Libraries: Ticket #2890: Boost.Build PDF docs broken

owner changed; cc set

Daniel James — Fri, 27 Mar 2009 08:43:31 GMT

cc daniel_james@… added
owner changed from Daniel James to René Rivera

I'm reassigning this to Rene as I'd like his feedback below and I can't see any way to cc him. I'm not expecting to fix this.

The link is broken in the main release as well (you can see it in the inspect report). Older versions of boost seem to be fine, so you might want to do whatever you used to do.

As you're already changing links in your release script, you could use an absolute link in the main boost release and then change to it a relative link for the build release.

At the moment, we can't copy userman.pdf to the location on the site (I assume that's what you meant) as the documentation is served from the release zip file. It's possible to change htaccess to check for files before running php to get the page. Rene, does that sound okay to you? It's not very nice to have special cases, but that seems to be the least problematic way to me.

Incidentally, you should have as much access to the site as I have. Everything I do is through subversion.

anonymous — Mon, 29 Nov 2010 05:01:00 GMT

Is this still an issue? Apparently John has been able to build the PDF docs lately (from memory, I read something from the developers mailing list about his progress). Should we host the pdf files somewhere and just get the absolute link added to the documentation?

Daniel James — Sat, 11 Dec 2010 14:16:04 GMT

This is still an issue. You can see it in the latest version. This is something that needs to be fixed in boost build, as the broken link is present in the boost distribution.

Building the pdf docs is a different issue, it's still broken on the release branch due to moving the jam directory, but it's okay on trunk. I think it just needs [64189] to be merged.

status changed; resolution set

René Rivera — Wed, 31 Dec 2014 15:36:24 GMT

status new → closed
resolution → invalid

Assuming this is now either not a problem any more, or a different problem now that we are in github.