From: Jan Stary <hans@stare.cz>
To: discuss@mandoc.bsd.lv
Cc: groff@gnu.org, man-db-devel@nongnu.org
Subject: Re: Behaviour of .so differs between mandoc and groff
Date: Thu, 4 May 2023 08:18:51 +0200 [thread overview]
Message-ID: <ZFNOS5IrrOxjoclS@www.stare.cz> (raw)
In-Reply-To: <874josy77n.fsf@ada>
> > The problem with symlinks is that they need to be updated to match
> > manpage compression. `.so` works with any compression used for the
> > manpage.
That's not a problem with symlinks,
but a problem with manpage compression.
Why would anyone compress manpages?
How much space does that save overall?
OpenBSD:
43.6M /usr/share/man/
36.6M /usr/local/man/
17.4M /tmp/man.tar.gz
macOS:
133M /Library/Developer//CommandLineTools/SDKs/MacOSX13.3.sdk/usr/share/man
25M /usr/share/man/
57M /tmp/man.tar.gz
Tens of megabytes saved, in the whole system.
Absoultely not worth the hassle.
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2023-05-04 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 4:21 Alexis
2023-04-29 23:24 ` Alexis
[not found] ` <20230430120555.3mydcm7qmbsf75v6@illithid>
2023-05-03 0:27 ` Alexis
2023-05-04 5:44 ` Alexis
2023-05-04 6:18 ` Jan Stary [this message]
2023-05-04 7:13 ` Alexis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZFNOS5IrrOxjoclS@www.stare.cz \
--to=hans@stare.cz \
--cc=discuss@mandoc.bsd.lv \
--cc=groff@gnu.org \
--cc=man-db-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).