Bug#627332: update mlocate database?
On Thu, May 19, 2011 at 10:01:22PM +0200, intrigeri wrote:
> Colin Watson wrote (19 May 2011 16:04:17 GMT) :
> > Do you think that it would be OK to do this by default (see attached
> > patch), or do you want it to be more configurable?
> I'm no live-build maintainer, but any proposal of adding more to
> lb_chroot_hacks makes me a bit nervous and think of other ways to
> achieve the same result.
Sure, I understand the caution; I'm also willing to consider local
hooks, but given that what I'm doing is attempting to convert the
official Ubuntu live CD builds to live-build, I'd really rather get to
the point where 'lb config --mode ubuntu <some options>' is as close as
possible to the output we have with our previous system, without the
need for custom hooks. Thus, I'm going through the differences between
filesystems generated by the two systems and trying to resolve them.
> E.g. wouldn't it be nicer to add a (low-priority, disabled by default)
> debconf option to mlocate, that would update the mlocate db in
> mlocate.postinst when it is enabled? This way, everyone (rather than
> Debian Live users only) would get a way to opt-in for the
> "ready-to-work mlocate once installed" functionality by preseeding the
> package. Some Debian Derivatives might want to enable it.
There's no particular guarantee that mlocate.postinst runs sufficiently
late in the process for the locate database to be reasonably complete
(it would probably be after the bulk of files have been unpacked, but it
would really be better if this were done as close to the end as
possible). Triggers don't really offer the right interface either, and
in any case doing something like 'interest /' in a triggers file would
likely slow the whole process down unreasonably.
Colin Watson [firstname.lastname@example.org]