https://bugzilla.redhat.com/show_bug.cgi?id=1754964 --- Comment #10 from Neal Gompa <ngompa13@xxxxxxxxx> --- (In reply to Miro Hrončok from comment #8) > (In reply to Neal Gompa from comment #6) > > > > > ln -s brz.1 %{buildroot}%{_mandir}/man1/bzr.1 > > > > > > > > This doesn't do *exactly* the thing you expect. Do something like this: > > > > > > > > > # Link bzr(1) to brz(1) > > > > > echo ".so man1/brz.1" > %{buildroot}%{_mandir}/man1/bzr.1 > > > > > > > > This ensures man-db does the correct thing for references. > > > > > > Could you please describe the difference? It sound interesting, I've always > > > just linked the manual page (I remember it was broken before due to the way > > > the Builrtoot Policy handled compression, but that works fine now). > > > > > > > > > > If you do a "man 1 bzr" with this, man's cached references will pull brz(1). > > I don't understands the difference here, sorry. > > When I link it via "ln -s", what will "man 1 bzr" do? > When I link it via ".so man1/brz.1", what will "man 1 bzr" do? > > > > It also allows manpage indexers to Do The Right Thing(TM) and re-point > > references. > > > > For example: https://www.mankier.com/1/pkg-config will actually redirect to > > https://www.mankier.com/1/pkgconf instead of just being a copy. > > python3.spec has: > > ln -s ./python3.1 %{buildroot}%{_mandir}/man1/python.1 > > But https://www.mankier.com/1/python redirects to > https://www.mankier.com/1/python3 > > > > There's a few other benefits, mostly related to the web of man page > > dependencies and how they're handled by man page parsers. > > > > I don't know why this isn't documented or made into a macro, but it probably > > should be. It's a very useful trick! > > This should be part of the guidelines, if it really matters (although I am > not quite understand that yet). The symlink trick used to not work, I guess presumably because of the auto-compression thing freaking out on symlinks. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
