public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Chris J. Breisch" <chris.ml@breisch.org>
To: cygwin@cygwin.com
Subject: Re: Updated Cygwin yesterday, makewhatis is not present on my system
Date: Wed, 02 Jul 2014 12:04:00 -0000	[thread overview]
Message-ID: <53B3F530.6030000@breisch.org> (raw)
In-Reply-To: <CAFWoy7GEdzSKSACf_YMSEEL5Enu2VNZF7CHXJ1inu9y2-w48xQ@mail.gmail.com>

Keith Christian wrote:
> Chris,
>
> So (I'm talking to you as if you are the maintainer of man-db....(are
> you?)) mandb sounds like the man system Debian uses, where (at least a
> few years ago) the whatis database is created by invoking "mandb -C."
>
> Testing this - "mandb" alone creates the databases, even though there
> is a "-c" argument to"mandb," which I am running at this moment.
> "mandb -c" is emitting errors as it runs, "can't open," "bad symlink,"
> "whatis parse for xxxxxx failed," etc.
>
> Ok, I think I have figured it out.  Will the now unnecessary files
> created by "makewhatis" be purged or overwritten by mandb?
>
> Keith
>

Yes, I'm the maintainer.

mandb -c creates the database, and will generate warnings. You likely 
already had a database created though, as that's handled when you 
install mandb.

mandb without any arguments updates the database, and mandb -q updates 
it quietly.

Oh, that's a good question about the unnecessary files. I should add 
that cleanup to the install scripts, since it obsoletes man.





-- 
Chris J. Breisch

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2014-07-02 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 19:20 Keith Christian
2014-07-01 19:26 ` Chris J. Breisch
2014-07-01 20:47   ` Keith Christian
2014-07-01 22:05     ` Andrey Repin
2014-07-02 12:04     ` Chris J. Breisch [this message]
2014-07-02 12:50       ` Andrey Repin
2014-07-02 14:09         ` Chris J. Breisch
2014-07-02 12:59       ` Keith Christian

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=53B3F530.6030000@breisch.org \
    --to=chris.ml@breisch.org \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).