From: Baptiste Daroussin <bapt@FreeBSD.org>
Subject: Re: Allow gzipped .so and search .so in manpath
Date: Sat, 29 Nov 2014 18:54:08 +0100 [thread overview]
Message-ID: <20141129175408.GD88765@ivaldir.etoilebsd.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 3030 bytes --]
On Thu, Nov 27, 2014 at 01:12:42AM +0100, Ingo Schwarze wrote:
> Hi Baptiste,
> Baptiste Daroussin wrote on Wed, Nov 26, 2014 at 09:24:13PM +0100:
> > I was expecting the above :)
> I just committed the two following patches, and i believe they
> resolve the issue.
> There is still a minor problem in makewhatis(8) with database
> generation when .so to .gz is involved, but i'll get round to that.
> Note that -current is at
> today, mdocl.bsd.lv is a few days old. I'm right in the middle of
> switching the server to new hardware. It will be back at mdocml
> tomorrow, or in a few days at the latest.
> > What about using zlib directly, that could simplify a bunch of things.
> That idea makes sense to me. However, i want to do the 1.13.2
> release without adding any new dependencies to help the downstream
> projects to stabilize and/or migrate to the 1.13 series. Granted,
> libz is all but heavyweight, and it's hard to imagine there might
> be anybody out there who doesn't have it, but anyway...
> I'd rather return to that idea after the 1.13.2 release.
> > Right now in the ports tree I'm ripping them at package creation
> > using soelim from groff and I wrote minimalistic version in base
> > to be able to continue using that when groff will be removed.
> Sounds reasonable.
> When dealing with pure .so files, i.e. those containing a single .so
> request and nothing else, it would even be better to replace them with
> hard links instead of having two files with the same content - not so
> much because that saves space, but rather because it allows combining
> information in mandoc.db(5)/apropos(1).
> For the user, the end result looks like this:
> With copies of files:
> $ apropos getuid
> geteuid(2) - get user identification
> getuid(2) - get user identification
> With hard (or soft or .so) links:
> $ apropos getuid
> geteuid, getuid(2) - get user identification
> The latter not only saves screen real estate, but also helps to
> realize both are documented in the same manual page.
Yes that makes sense, I'll look in that direction, I ll see what I can cook for
Shouldn't the look up for .so links be done in the manpath.
For example I have the WindowMaker manpage (which should really be a link in
that case :D) installed here:
The content is the following:
If I run:
mandoc: man1/wmaker.1x: SYSERR: No such file or directory
mandoc: man1/wmaker.1x:1:19: FATAL: .so request failed: .so man1/wmaker.1x
If I trace it it tries to open man1/wmaker.1x then man1/wmaker.1x.gz but in the
directory where I run the command.
zshall(1) is a better example as in this it cannot be replaced by links.
[-- Attachment #2: Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-11-29 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 14:36 Baptiste Daroussin
2014-11-26 20:10 ` Ingo Schwarze
2014-11-26 20:24 ` Baptiste Daroussin
2014-11-27 0:12 ` Ingo Schwarze
2014-11-27 2:03 ` Ingo Schwarze
2014-11-29 17:54 ` Baptiste Daroussin [this message]
2014-11-29 18:14 ` Ingo Schwarze
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).