Ticket UUID: | 01b77111e55b108bbebb2a0ee599b4d67735ce3b | |||
Title: | Broken Links on www.tcl.tk/man/tcl8.6 | |||
Type: | Bug | Version: | 8.6.1 | |
Submitter: | dkf | Created on: | 2013-10-25 14:53:06 | |
Subsystem: | None | Assigned To: | dgp | |
Priority: | 9 Immediate | Severity: | Critical | |
Status: | Closed | Last Modified: | 2016-08-20 16:03:51 | |
Resolution: | Works For Me | Closed By: | dkf | |
Closed on: | 2016-08-20 16:03:51 | |||
Description: |
If I go to the 8.6 manpages online, I get links to docs of contributed packages. All of which are broken except for the one for SQLite. For example, “TDBC Package Commands” (in the heading part) does not lead anywhere. | |||
User Comments: |
dkf added on 2016-08-20 16:03:51:
Seems to be working now. dkf added on 2013-11-03 10:50:39: I should also note that merely adding a package doesn't require the mapping to be updated, provided that the default mapping (with string totitle IIRC) is enough. dkf added on 2013-11-02 22:24:46: Well, the package.list.txt is the only way to get the correct mapping between package directory root name and documented package name. I've not found anything in any of the packages that gives this information; it's not in the configure.in or the README or the documentation files. As far as curation overhead goes, it's tiny. Certainly smaller than the effort of actually finding which version of the packages to distribute. dgp added on 2013-10-30 17:08:53: The good news here is that the distributed documentation release tcl8.6.1-html.tar.gz generated by `make html` is in fine shape. No broken links in it. The failures showed up entirely in my transference of the files in that distribution onto the web server machine. dgp added on 2013-10-29 19:15:24: I have to catch up on this. One thing I see already committed which I will try to undo is the distribution of the "package.list.txt" file. That was *not* an oversight. It was intentionally and explicitly not made part of the source code distribution. If we truly have to change to a fully cataloged and curated system to make bundled packages work, then the whole system needs a re-think. The explicit intent has been to *not* have manifests or catalogs or anything like that but have the build harness just discover the set of bundled packages as they happen to be or not be present under tcl/pkgs. dkf added on 2013-10-28 09:24:27: I've done what fixes I can do; the one thing I can't (or at least don't know how to) is push a new doc build to www.tcl.tk. dkf added on 2013-10-27 18:04:53: OK, it appears that the problem was that make install was not done before make html. Starting with the distribution archives of Tcl and Tk, unpacked next to each other, and then installed (e.g., in /tmp) before doing the doc build, I get a complete and working documentation set. Except for one minor bug in link recognition in a third-party package. dkf added on 2013-10-27 17:42:49: Note that this might be due to problems in the deployment — e.g., only deploying part of the documentation build — or something going wrong with the link generation. This has been mentioned on comp.lang.tcl. |