On Sun, May 02, 2021 at 03:07:47PM -0600, Chris Murphy wrote: > On Thu, Apr 29, 2021 at 8:21 PM Dominique Martinet > <asmadeus@xxxxxxxxxxxxx> wrote: > > > > (added mlocate maintainer msekleta in Ccs; hopefully that's a still > > valid address) > > > > Zbigniew Jędrzejewski-Szmek wrote on Sat, Feb 20, 2021 at 02:06:00PM +0000: > > > Debian is apparently switching to plocate as the the default > > > locate/mlocate provider [0], a bit faster and more disk-efficient. > > > Would it make sense to do the same in Fedora? > > > > > > I prepared a package [1, 2]. The code seems nice and clean enough. > > > I'd be happy to take it through review, but I'm not particular keen > > > on long-term maintenance… > > > > Having just tried I think it'd make sense, the difference is striking. > > Small db update is a bit slower but that's a background activity, and > > search really feels instant (tens of ms) compared to a handful of > > seconds. > > > > > > I think that'll require a bit more work though, and we can start by just > > having the package available it doesn't have to be the default right > > away (I remembered that there was a discussion but not where it had > > ended, so was surprised to find no package in main repos!) > > Unless there's a significant impediment to making it the default in > Fedora 35, I think we should just move forward. I agree. Plocate/mlocate is useful technology, but it's not important enough to justify maintaining two or three different implementations. If we can make plocate cover all bases, and it's faster, I'd just make it *the* implementation. Let's get the agreement of mlocate maintainer first though. Michal, wdyt? > updatedb does not index /home when /home is a bind mount (75 comments) > https://bugzilla.redhat.com/show_bug.cgi?id=906591 > > Summary: Upstream sets PRUNE_BIND_MOUNTS to "no". For some reason > Fedora has it set to "yes". Because both rpm-ostree and Btrfs make use > of bind mounts, updatedb doesn't index /home at all. Silverblue setups > comment the PRUNE_BIND_MOUNTS = "yes" line out, so the problem doesn't > happen on Silverblue. But it still is a problem on default desktops, > and I still don't know why we don't just do either what upstream or > Silverblue are doing. > > So I'm kinda curious if plocate will have issues related to bind > mounts or if it does things differently. 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
