Re: Bug#58640: wrapper does not handle fakeroot well
- To: Joey Hess <firstname.lastname@example.org>
- Cc: Colin Phipps <email@example.com>, firstname.lastname@example.org
- Subject: Re: Bug#58640: wrapper does not handle fakeroot well
- From: Fabrizio Polacco <email@example.com>
- Date: Thu, 24 Feb 2000 12:47:45 +0200
- Message-id: <20000224124744.A450@none>
- In-reply-to: <20000223084333.I25838@kitenet.net>; from firstname.lastname@example.org on Wed, Feb 23, 2000 at 08:43:33AM -0800
- References: <20000221145227.A679@globix.net> <20000222093122.D2402@none> <20000222193431.A624@crp22.trin.cam.ac.uk> <20000223010454.E5083@plato.localdomain.local> <20000223131726.B991@crp22.trin.cam.ac.uk> <20000223084333.I25838@kitenet.net>
On Wed, Feb 23, 2000 at 08:43:33AM -0800, Joey Hess wrote:
> have a sneaking suspicion that I have waited longer for mandb to run when
> I'm just wanting to get a man page, than caching preformatted manpages has
> ever saved me.
This is only because you use rarely man and install packages often.
Each package install manpages, and this triggers the scan of that
directory on the very next issue of man.
This could be avoided if we could put in place the automatic updating of
the database when dpkg has finished installing, something like the
deferred call to update-menus.
It would be very great if this deferring mechanism used by update-menus
can be generalized and you can put in your postinst something like:
test -x $(which run-after-dpkg) -a -x $(which mandb) && run-after-dpkg mandb -q
(not mandb --create !!!)
Another and more clean (but ...) would be if dpkg runs mandb --quiet
when exiting (maybe when it has installed some manpages, but even always
would be acceptable: try running it twice and you'll see ... it just
stats few directories and compares the timestamps with the indexes).
| email@example.com firstname.lastname@example.org
| pgp: 6F7267F5 57 16 C4 ED C9 86 40 7B 1A 69 A1 66 EC FB D2 5E
| email@example.com gsm: +358 (0)40 707 2468