Opened 14 years ago
Closed 8 years ago
#2890 closed Bugs (invalid)
Boost.Build PDF docs broken
| Reported by: | Vladimir Prus | Owned by: | René Rivera |
|---|---|---|---|
| Milestone: | Boost 1.39.0 | Component: | Documentation |
| Version: | Boost 1.38.0 | Severity: | Problem |
| Keywords: | Cc: | daniel_james@… |
Description
Edward Diener has reported that the link to PDF documentation on http://www.boost.org/doc/libs/1_38_0/tools/build/v2/index.html does not work. This is relative link presently, and it works fine on http://boost.org/boost-build2. I see two ways of fixing it in the complete Boost docs:
- Copy userman.pdf into
- Change the document to use absolute link to PDF file
I'd appreciate guidance as to which option is best. If first option is best, then naturally it should be done by somebody with access to the site.
Change History (4)
comment:1 by , 14 years ago
| Cc: | added |
|---|---|
| Owner: | changed from to |
comment:2 by , 12 years ago
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?
comment:3 by , 12 years ago
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.
comment:4 by , 8 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Assuming this is now either not a problem any more, or a different problem now that we are in github.
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.