Thursday, 23 May 2019

Re: mlocate - what is it good for?

On Wed, May 22, 2019 at 11:25:45PM -0700, Bryan Quigley wrote:
> The mentioned Debian bug #880507 is one of the advantages of moving from
> cron to systemd units -see proposed unit file in [1]. The timers in
> systemd are really perfect for this...
>
> I use locate all the time. I really like how much simpler it is then
> find. I don't have to think to usually get what I'm looking for. I'm
> going to experiment with using grep <filename> /var/lib/dpkg/info/*.list as
> the majority of files I run locate for are from packages..
>
> From a product perspective it does make sense to remove:
> * Desktop has tracker installed by default. The majority of users will
> use that instead as it's integrated with the GUI.

Did this change? It's not installed by default in bionic; and no meta
package depends on it, but it seems to have moved to main in disco.

I think both tracker and locate can offer a terrible user experience for
a lot of users, due to I/O load after resume/boot; but tracker also has
a ton of CPU usage extracting stuff from documents and putting the text
into its xapian (?) db.

> * The majority of cloud/server deployments aren't interactive these days.
> It's a waste there.

ack - also, it sucks to have this I/O load once a day.

>
> They key group I can see wanting it are developers - who can install it.

ack


--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel