Re: F36 Change: Plocate as the default locate implementation (Self-Contained Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 01, 2021 at 08:55:44PM +0000, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Dec 01, 2021 at 02:13:07PM -0500, Chris Murphy wrote:
> > On Tue, Nov 23, 2021 at 4:54 PM Zbigniew Jędrzejewski-Szmek
> > <zbyszek@xxxxxxxxx> wrote:
> > >
> > > On Tue, Nov 23, 2021 at 01:52:43PM -0500, Chris Murphy wrote:
> > > > On Tue, Nov 23, 2021 at 12:19 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote:
> > > >
> > > > > == How To Test ==
> > > > > # Install `plocate` (`sudo dnf install plocate --allowerasing`)
> > > > > # Wait for `plocate-updatedb.service` to finish (`sudo systemctl start
> > > > > plocate-updatedb.service`)
> > > > > # Use `plocate pattern` or `plocate -r <regexp>` to search for files.
> > > >
> > > > Works for me. Also fixes this old bug where mlocate pruned bind mount
> > > > locations, which resulted in /home on Btrfs not being indexed.
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=906591
> > > >
> > > > Note for laptop users, plocate-updatedb.service contains
> > > > ConditionACPower=true, so if you're getting errors locating files, it
> > > > might be because the initial database isn't being created because no
> > > > AC power.
> > >
> > > Ack. (I assume that most people have the laptop on AC at least some
> > > of the time, so the db will get updated sooner or later. In the worst
> > > case, if the laptop is only charged while off or suspended, it would be
> > > necessary to remove the conditional. But I think that's a rare case, and
> > > the default is good.)
> > >
> > > > > == User Experience ==
> > > > > Users should not notice the difference. Installing `plocate`
> > > > > automatically removes `mlocate`. The new implementation is generally
> > > > > compatible with the old one in all common cases, and provides some
> > > > > additional options.
> > > >
> > > > I'm definitely noticing a difference. I'm not sure it was ever correct
> > > > that updatedb.conf was pruning bind mounts on Fedora. It's not the
> > > > mlocate default, but it is what Fedora has been using for years
> > > > (defacto default on Fedora).
> > >
> > > That's a known-fixed bug. I didn't mention it because, well, it was
> > > considered a bug in mlocate. ¯\_(ツ)_/¯
> > 
> > It's not a fixed bug.
> 
> Sorry, I meant that it's fixed in plocate, which simply does exhibit
> this behaviour.

Ah, OK, this has been cleared up in another part of the thread ;)

Zbyszek
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux