[doc][geometry][gil][signals] Broken links for Boost 1.70
Hi, On https://www.boost.org/doc/libs/1_70_0/ links to these documentations are broken: https://www.boost.org/doc/libs/1_70_0/libs/geometry/index/doc/html/index.htm... https://www.boost.org/doc/libs/1_70_0/libs/geometry/extensions/doc/html/inde... https://www.boost.org/doc/libs/1_70_0/libs/gil/doc/html/index.html https://www.boost.org/doc/libs/1_70_0/libs/signals/ Could anyone help to identify what is going wrong with those and how to fix it? p.s. I considered posting to boost-docs but that list seems inactive. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
Mateusz Loskot Via Boost wrote:
On https://www.boost.org/doc/libs/1_70_0/ links to these documentations are broken:
https://www.boost.org/doc/libs/1_70_0/libs/geometry/index/doc/html/index.htm... https://www.boost.org/doc/libs/1_70_0/libs/geometry/extensions/doc/html/inde... https://www.boost.org/doc/libs/1_70_0/libs/gil/doc/html/index.html https://www.boost.org/doc/libs/1_70_0/libs/signals/
Could anyone help to identify what is going wrong with those and how to fix it?
Regarding Geometry, we're discussing it here: https://github.com/boostorg/geometry/issues/585 The issue was introduced after I attempted to fix failures reported in our regression testing due to lack of metadata for sublibraries: https://github.com/boostorg/geometry/issues/575 To make things worse I also made a mistake and pushed extensions directory which should be only in develop branch into master branch. I already attempted to fix this by modifying the redirection in index.html files of sublibs: https://github.com/boostorg/geometry/commit/70994a3a320440d040925247d637480e... and I'm waiting for the develop and master versions of documentation to update to see if it works, e.g.: https://www.boost.org/doc/libs/develop/#lib-geometry Since we're on this subject. Is is possible to hide a sublib from being displayed on this list? During the discussion about the issue (585) we noticed that the script generating the documentation supports some kind of hiding of libraries (see: https://github.com/boostorg/website/blame/master/doc/libraries.json.php#L15-...) but we do not know if it's possible to hide specific sublibs and how to do it. Adam
Hi, I also noticed these broken links in the boost documentation for geometry. It made me wonder, whether there are more dead links in the boost documentation, so I tried to check that with a JS script. I only managed to get parts of the website running locally, and I didn't scan older versions than 1_70_0 recursively, so my results are definitely incomplete, but I did discover more broken links: The following documents list pages and below those pages is an unordered list of hyperlinks on those pages that seem to be broken. internal links that are probably broken: http://46.101.197.7/internal.html external links that are probably broken: http://46.101.197.7/external.html I'm not claiming that these lists are complete or without false positives but all links on it, that I checked manually, seem to be dead. Maybe the lists still help to see some broken links that might have gone unnoticed so far. Since link rot is natural, I wonder whether it would make sense to implement some check for this in the CI for the website so that breakages like this one could be discovered automatically in the future. I'd volunteer to implement that later this year but only if the general idea is considered sensible or viable by the boost website maintainers. Best regards, Tinko Bartels -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html
A link-checking checking tool called inspect.exe is already in existence
https://www.boost.org/doc/libs/1_70_0/tools/inspect/
and in use in an attempt to name'n'shame authors, but sadly not every library
author acts on it to update or remove links (a tiresome task).
Authors do not seem to use it when developing their documentation but building
the tool inspect.exe (jamfile provided so painless) and running it in the folder
containing their /html to create a local check.
(This tool also makes some other checks for other common mistakes (most common
is failure to prevent MAX and MIN macros being used when calling
numeric_limits<>::max() and min()).
But thanks for re-raising this issue.
Paul
Paul A. Bristow
Prizet Farmhouse
Kendal, Cumbria
LA8 8AB UK
-----Original Message-----
From: Boost
On Mon, Apr 15, 2019 at 5:47 PM Mateusz Loskot via Boost
On https://www.boost.org/doc/libs/1_70_0/ links to these documentations are broken:
... https://www.boost.org/doc/libs/1_70_0/libs/signals/
Could anyone help to identify what is going wrong with those and how to fix it?
signals [v1] was deprecated in 1.54.0, warned to be removed in 1.68.0, and removed in 1.69.0
Boost - Dev mailing list wrote
On Mon, Apr 15, 2019 at 5:47 PM Mateusz Loskot via Boost <
boost@.boost
> wrote:
On https://www.boost.org/doc/libs/1_70_0/ links to these documentations are broken:
... https://www.boost.org/doc/libs/1_70_0/libs/signals/
Could anyone help to identify what is going wrong with those and how to fix it?
signals [v1] was deprecated in 1.54.0, warned to be removed in 1.68.0, and removed in 1.69.0
It's still linked from the docs front page. ML ----- -- Mateusz Loskot, http://mateusz.loskot.net -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html
participants (5)
-
Adam Wulkiewicz -
James E. King III -
Mateusz Loskot -
pbristow＠hetp.u-net.com -
Tinko Bartels