Hi, Jason McIntyre wrote on Mon, Apr 29, 2019 at 11:26:43PM +0100: > On Tue, Apr 30, 2019 at 12:16:10AM +0200, Marc Espie wrote: >> On Sun, Apr 28, 2019 at 02:16:23PM -0500, Tim Chase wrote:
>>> Dangling SEE ALSO references to man-pages that don't exist: >>> >>> dig(1) references missing named(8) and dnssec-keygen(8) >>> host(1) references missing named(8) >>> nslookup(1) references missing named(8) >>> info(5) references missing emacs(1) >>> info(5) references missing tex(1) >>> texinfo(5) references missing emacs(1) >>> texinfo(5) references missing tex(1) >>> readline(3) references missing bash(1) >> Now, all of these DO exist, in the ports tree. >> >> Question: should the base system manpages be self-contained 100%, or is >> it better to also point people to optional software that may or may not >> be installed ?.. > i hate it when we Xr outside base, but sometimes it just makes sense. >> I believe there's no 100% correct answer. > i agree. >> For instance, info mode in emacs and the relationship between .texi >> and the TeX formatter are tight enough that I believe those references >> are innocuous. I agree with both of you. In addition to what you already said, here are additional reasons to not patch away these particular cases: * All of them are in third-party software and patching them away increases diffs from upstream for minor benefit, if any. * All of these reference the third-party software context where they come from, so this is about providing context in addition to providing access to additional reference information. * All of them are in man(7) rather than in mdoc(7) format, where the concept of a "cross reference" is much less clearly defined in the first place and where cross references do not result in <a href> elements in HTML output, i.e. these do not even cause dead links, at least not yet, and they do not even cause mandoc -T lint warnings, and likely never will. Yours, Ingo
