Bug#627332: update mlocate database?
On 05/19/2011 06:04 PM, Colin Watson wrote:
This is convenient because you get to use locate in
the live session without having to wait for updatedb, and because after
you install the system it doesn't have to do very much work to update
the locate database
The trade-off is that the database takes a bit of space; it's about half
a megabyte compressed here for a 700 megabyte squashfs. However, this
should scale with the size of the image, so I think it's reasonably
agreed. that's not really much for having it included by default (if
mlocate is installed).
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'd appreciate some
guidance on this, as I haven't quite got a feel yet for what you
consider to be good practice in live-build.
if it's reasonable for a 'standard' desktop image, then a feature should
be enabled by default, and generally, things should always (i know that
it's currently not the case) be configurable as fine-graned as possible
as long as it makes sense. there are a few things that really don't make
much sense or are really edgecases (e.g. not removing the udev
persistent net rules is a very, very rare case i think).
i'll probaly rework the lb_chroot_hacks file a bit tomorrow, and include
your patch with it (and an option to disable it).
Address: Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern