Re: mandocdb: full set of search types

[Kristaps Dzonsons <kristaps@bsd.lv>]

On 16/11/2011 01:39, Ingo Schwarze wrote:
> Hi,
>
> we are close to going into production.  I have talked to espie@,
> and he is d'accord with putting small pieces into
>    /usr/src/libexec/makewhatis/Makewhatis.pm
> to call out to mandocdb(8) for automated updates of the mandoc.db
> files alongside the updates of the whatis.db files when installing
> and removing packages, such that people running -current can easily
> start testing the new apropos.
>
> We will keep the old makewhatis/apropos-combo in place until the new
> system is reasonably feature-complete and clearly better than the
> old one, then install the new apropos in place of the old one and
> finally remove the old components.
>
> Before enabling mandocdb in pkg_add(8), i'd like to get the database
> format complete, such that we don't force people to rebuild the
> databases after upgrading to new snapshots.
>
> Here is a patch defining TYPE_ flags for all macros that i can
> imagine might be worth searching for (maybe even a few more, but i'd
> rather have too many than too few).  I have left out all obsolete
> macros and most physical formatting macros.
>
> This requires switching the mask to 64 bits.  During the switch,
> i have replaced the very error-prone handling of the key database
> values by a new struct db_val; some memcpy() calls by normal
> assignments; and some magical constants by sizeof() constructs.
>
> OK to put this in, or do you see anything that is missing?
>
>
> Right now, i will start to implement the new search types.

Hi Ingo,

Just a word or two before I sleep.  This approach is sound and I've no 
issues with a quick look over the patch, but will wait til tomorrow to 
do so in earnest.  But first, before mandocdb gets production, the 
database should be checked for endian-neutrality.

Second, we'd long ago mentioned splitting SYNOPSIS-invoked macros (Fl, 
Fn, etc.) for querying on their SYNOPSIS or non-SYNOPSIS usage.  I think 
an elegant method is to encode the section within the keyword database, 
which allows for

  apropos Fn~mdoc -a -s SYNOPSIS

or whatever `-s' replacement operator.  How does that sound?  This 
sounds a lot more reasonable than encoding separate Fn, Nm, etc. macros 
for SYNOPSIS and non-SYNOPSIS invocation.

Thoughts?

Kristaps
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv