help / color / mirror / Atom feed
From: Ingo Schwarze <>
To: Baptiste Daroussin <>
Subject: Re: support another man.conf(5) format or extending it
Date: Thu, 27 Nov 2014 01:43:55 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Baptiste,

Baptiste Daroussin wrote on Mon, Nov 24, 2014 at 01:50:19PM +0100:

> While working on integrating mandoc(1) into FreeBSD I have not yet
> integrated apropos and makewhatis because of the difference of format
> of man.conf(5).
> Will you be against that I modifiy the man.conf(5) parser so that
> is does support a minimum set of the FreeBSD's man.conf(5) ?

I don't see any other way to solve that issue.

> BAsically I'm think about mostly:

Seems reasonable.

The man.conf(5) format itself is refreshingly simple.
I hate all kinds of *.d configuration directories,
but well, maybe it's a matter of taste and we need
to deal with it in any case.

If you volunteer to prepare a patch, i'll see whether i can
commit it as is, or otherwise edit it a bit to better fit
into the framework.

Probably, switching will be done at ./configure time and
with #if directives.  I might need some help how to best
let ./configure detect your flavour of man.conf(5).

> Here is the manpage of FreeBSD's version of man.conf(5)
> Btw I think I'll try to make FreeBSD tracking the CVS version
> of mdocml rather than the releases now because the CVS version
> works way better for me :)

Feel free if you want to.  I'm doing the same in OpenBSD.
It makes sense if you maintain it very actively.  Most other
downstream projects prefer the less exciting way of tracking
releases, but both are fine when done properly.

> Btw here is a small patch to fix build when HAVE_MANPATH is set.

Committed, thanks.

> Index: manpath.c
> ===================================================================
> RCS file: /cvs/mdocml/manpath.c,v
> retrieving revision 1.18
> diff -u -r1.18 manpath.c
> --- manpath.c	18 Nov 2014 19:41:47 -0000	1.18
> +++ manpath.c	24 Nov 2014 11:26:19 -0000
> @@ -80,7 +80,7 @@
>  	if ( ! ferror(stream) && feof(stream) &&
>  			bsz && '\n' == buf[bsz - 1]) {
>  		buf[bsz - 1] = '\0';
> -		manpath_parseline(dirs, buf);
> +		manpath_parseline(dirs, buf, 1);
>  	}
>  	free(buf);
 To unsubscribe send an email to

      reply	other threads:[~2014-11-27  0:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 12:50 Baptiste Daroussin
2014-11-27  0:43 ` Ingo Schwarze [this message]

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:

* 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).