Replacing mlocate with plocate
Yo! I'm going to drop `mlocate` from the repositories and provide `plocate` as the default locate in Arch Linux. mlocate is very much an abandoned project, while plocate is a modern implementation with a faster database implementation along with io_uring support. https://plocate.sesse.net/ The question is if people feel a strong desire to keep a locate implementation in `[core]` or if we are fine with this living inside `[extra]`. Adding `plocate` to `[core]` would mean we would need to move a `liburing` to `[core]` and I don't really know if we need that. Any opinions? -- Morten Linderud PGP: 9C02FF419FECBE16
Am 24.08.24 um 12:03 schrieb Morten Linderud:
Yo!
I'm going to drop `mlocate` from the repositories and provide `plocate` as the default locate in Arch Linux.
mlocate is very much an abandoned project, while plocate is a modern implementation with a faster database implementation along with io_uring support.
The question is if people feel a strong desire to keep a locate implementation in `[core]` or if we are fine with this living inside `[extra]`. Adding `plocate` to `[core]` would mean we would need to move a `liburing` to `[core]` and I don't really know if we need that.
Any opinions?
Hi Morton, I would be fine with it in [extra]. Best regards tpowa -- Tobias Powalowski Arch Linux Developer (tpowa) https://www.archlinux.org tpowa@archlinux.org Archboot Developer https://archboot.com St. Martin-Apotheke Herzog-Georg-Str. 25 89415 Lauingen https://www.st-martin-apo.de info@st-martin-apo.de
Morten Linderud <foxboron@archlinux.org> on Sat, 2024/08/24 12:03:
Yo!
I'm going to drop `mlocate` from the repositories and provide `plocate` as the default locate in Arch Linux.
mlocate is very much an abandoned project, while plocate is a modern implementation with a faster database implementation along with io_uring support.
Sounds good.
The question is if people feel a strong desire to keep a locate implementation in `[core]` or if we are fine with this living inside `[extra]`. Adding `plocate` to `[core]` would mean we would need to move a `liburing` to `[core]` and I don't really know if we need that.
Any opinions?
IMHO it should go to [extra]. This package is all but critical. -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
On 2024-08-24 12:03:18 (+0200), Morten Linderud wrote:
The question is if people feel a strong desire to keep a locate implementation in `[core]` or if we are fine with this living inside `[extra]`. Adding `plocate` to `[core]` would mean we would need to move a `liburing` to `[core]` and I don't really know if we need that.
Any opinions?
I'm fine with it being moved to [extra]. Thanks for taking care of this! Best, David -- https://sleepmap.de
Thanks for the feedback everyone. I've pushed 1.1.22-2 of plocate which includes a replaces directive. It should replace mlocate from now on. Also included the patch that enables the updatedb timer by default. -- Morten Linderud PGP: 9C02FF419FECBE16
participants (4)
-
Christian Hesse
-
David Runge
-
Morten Linderud
-
Tobias Powalowski