Op 10-7-2014 8:20 Yaakov Selkowitz schreef:
On 2014-07-09 17:28, Keith Christian wrote:
There are other packages that require a bit of time post-install, such
as the texlive package. Having the man-db package update the DB
immediately after install sounds like a good idea, even if it takes a
few minutes.
We're talking 20 minutes or more, which is IMO excessive.
Else, end users that aren't familiar with re-creating the DB may be
discouraged at not finding something in the man pages.
That, or else use a non-blocking method of printing a message with the
DB creation command line.
There is another issue: creating it during man-db's postinstall only
helps for the manpages installed as of then; any pages added or
updated afterwards won't get into the DB. There is a way we could
handle that (similar to _update-info-dir), but only if DB generation
is faster.
Isn't there an option that man-db grows a database cache while you are
using it. Such that a page is added to the cache the first time you read
a man page. Then you have a small extra delay only the first time.
Usually people read only a small percentage of the man pages frequently.
Caching all man pages is a bit excessive.
Man-db also displays non-cached man pages. What is the time difference
between loading a cached or a non-cached page on Cygwin? Perhaps it's
not worth caching.
regards,
--
Erwin Waterlander
http://waterlan.home.xs4all.nl/
--
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
