Boost C++ Libraries: Ticket #2616: No link to "latest" version of a library https://svn.boost.org/trac10/ticket/2616 <p> Except for legacy libraries that have a suitable redirect link from <code>libs/</code><em>libraryname</em><code>/</code>, there is now no way to produce a link to the latest documentation for a given library. Also, the "permanent" redirects from <code>libs/</code><em>libraryname</em><code>/</code> keep getting updated to point at whatever the latest version happens to be. I'm no expert, but I'm guessing that's bad web practice. In addition to links like <a href="http://www.boost.org/doc/libs/1_37_0/doc/html/mpi.html">http://www.boost.org/doc/libs/1_37_0/doc/html/mpi.html</a> can't we also have <a href="http://www.boost.org/doc/libs/latest/doc/html/mpi.html">http://www.boost.org/doc/libs/latest/doc/html/mpi.html</a>? </p> <p> Also (separate feature), if I know the name of the library, can't you give me a reasonably short URL that will visit its latest docs without having to navigate there? That's especially bad if it's impossible (see <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/2490" title="#2490: Feature Requests: http://www.boost.org/doc/libs/1_37_0/libs/libraries.htm not reachable ... (closed: fixed)">#2490</a>). </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/2616 Trac 1.4.3 René Rivera Sat, 14 Feb 2009 19:37:46 GMT component changed https://svn.boost.org/trac10/ticket/2616#comment:1 https://svn.boost.org/trac10/ticket/2616#comment:1 <ul> <li><strong>component</strong> <span class="trac-field-old">None</span> → <span class="trac-field-new">website</span> </li> </ul> Ticket Daniel James Sat, 21 Feb 2009 17:48:04 GMT <link>https://svn.boost.org/trac10/ticket/2616#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2616#comment:2</guid> <description> <p> It'd be much easier to deal with this ticket if it was split into separate tickets for each request. </p> <p> For the main complaint, I'll make sure all the libraries have appropriate forwarding index files, I'm not sure why you think that <code>libs/library-name</code> only works for 'legacy' libraries, as I've been making sure that new libraries have them (eg <a href="http://www.boost.org/libs/flyweight/">http://www.boost.org/libs/flyweight/</a>). Although I haven't been doing that for sub-libraries (such as swap, which is part of utility), maybe I should. </p> <p> As for <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/2490" title="#2490: Feature Requests: http://www.boost.org/doc/libs/1_37_0/libs/libraries.htm not reachable ... (closed: fixed)">#2490</a>, did you see my comment? The categorized library list is now live and looks a lot like 'libs/libraries.htm'. </p> <p> I'm afraid that not going to reorganize the urls anytime soon, but you're wrong about the redirects. The permanent redirects go to the release url: </p> <pre class="wiki">$ curl -I http://www.boost.org/libs/python/ HTTP/1.1 301 Moved Permanently Date: Sat, 21 Feb 2009 17:33:07 GMT Server: Apache/2.0.52 (Red Hat) Location: http://www.boost.org/doc/libs/release/libs/python/ Content-Type: text/html; charset=iso-8859-1 </pre><p> This then gets a 302 redirect, which isn't permanent: </p> <pre class="wiki">HTTP/1.1 302 Found Date: Sat, 21 Feb 2009 17:34:35 GMT Server: Apache/2.0.52 (Red Hat) Location: http://www.boost.org/doc/libs/1_38_0/libs/python/ Content-Type: text/html; charset=iso-8859-1 </pre><p> Of course, most people won't be aware of the difference. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Dave Abrahams</dc:creator> <pubDate>Sun, 22 Feb 2009 17:54:26 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/2616#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2616#comment:3</guid> <description> <p> Replying to <a class="ticket" href="https://svn.boost.org/trac10/ticket/2616#comment:2" title="Comment 2">danieljames</a>: </p> <blockquote class="citation"> <p> It'd be much easier to deal with this ticket if it was split into separate tickets for each request. </p> </blockquote> <p> Sorry. Sometimes all I can muster is to put something in the tracker. </p> <blockquote class="citation"> <p> For the main complaint, I'll make sure all the libraries have appropriate forwarding index files, I'm not sure why you think that <code>libs/library-name</code> only works for 'legacy' libraries, as I've been making sure that new libraries have them (eg <a href="http://www.boost.org/libs/flyweight/">http://www.boost.org/libs/flyweight/</a>). </p> </blockquote> <p> Because it failed for me at least once, I drew that conclusion. </p> <blockquote class="citation"> <p> Although I haven't been doing that for sub-libraries (such as swap, which is part of utility), maybe I should. </p> </blockquote> <p> Prolly. </p> <blockquote class="citation"> <p> As for <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/2490" title="#2490: Feature Requests: http://www.boost.org/doc/libs/1_37_0/libs/libraries.htm not reachable ... (closed: fixed)">#2490</a>, did you see my comment? The categorized library list is now live and looks a lot like 'libs/libraries.htm'. </p> </blockquote> <p> Yes, I saw the comment. You should update the comment to say it's live. The fact that it's live doesn't make it reachable. I really do think "Libraries" should still be a top-level link on the home page. The libraries page is not only a set of docs, but a catalogue of what's in Boost. </p> <blockquote class="citation"> <p> I'm afraid that not going to reorganize the urls anytime soon, but you're wrong about the redirects. The permanent redirects go to the release url </p> </blockquote> <blockquote class="citation"> <p> Of course, most people won't be aware of the difference. </p> </blockquote> <p> Like me. OK, that's good to know; I'll use the release URL in the future. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Daniel James</dc:creator> <pubDate>Sun, 22 Feb 2009 18:14:08 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/2616#comment:4 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2616#comment:4</guid> <description> <p> I've added some 'quick links' to the welcome section on the sidebar on the beta site. Let me know what you think. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Dave Abrahams</dc:creator> <pubDate>Mon, 23 Feb 2009 22:41:34 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/2616#comment:5 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2616#comment:5</guid> <description> <p> I like it. However, shouldn't we be discussing <em>this</em> in <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/2490" title="#2490: Feature Requests: http://www.boost.org/doc/libs/1_37_0/libs/libraries.htm not reachable ... (closed: fixed)">#2490</a>? </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Dean Michael Berris</dc:creator> <pubDate>Sun, 28 Nov 2010 23:10:18 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/2616#comment:6 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2616#comment:6</guid> <description> <p> Should we consider this bug closed then? I am able to use /libs/library_name with no problems now. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Dave Abrahams</dc:creator> <pubDate>Mon, 06 Dec 2010 21:44:24 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/2616#comment:7 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2616#comment:7</guid> <description> <p> Yes, we can close it. The fact that the short link is a redirect is sub-optimal when it comes to search engines, but there you go. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Dave Abrahams</dc:creator> <pubDate>Mon, 06 Dec 2010 21:44:37 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/2616#comment:8 https://svn.boost.org/trac10/ticket/2616#comment:8 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> Ticket