blob: f205b9997243ddee83e58e0c0ad17a412bd4aa3a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
<maintainer type="person" proxied="yes">
<email>arsen@aarsen.me</email>
<name>Arsen Arsenović</name>
</maintainer>
<maintainer type="person" proxied="yes">
<email>jeffrey@icurse.nl</email>
<name>Jeffrey Lin</name>
</maintainer>
<maintainer type="person">
<email>flow@gentoo.org</email>
<name>Florian Schmaus</name>
</maintainer>
<maintainer type="person">
<email>sam@gentoo.org</email>
<name>Sam James</name>
</maintainer>
<maintainer type="project" proxied="proxy">
<email>proxy-maint@gentoo.org</email>
<name>Proxy Maintainers</name>
</maintainer>
<use>
<flag name="io-uring">Enable efficient I/O via <pkg>sys-libs/liburing</pkg>.</flag>
</use>
<longdescription>
plocate works by creating an inverted index over trigrams (combinations of
three bytes) in the search strings, which allows it to rapidly narrow down the
set of candidates to a very small list, instead of linearly scanning through
every entry. It does nearly all I/O asynchronously using io_uring if available
(Linux 5.1+), which reduces the impact of seek latency on systems without SSDs.
Like mlocate and slocate, the returned file set is user-dependent, ie. a user
will only see a file if find(1) would list it (all directories from the root
have +rx permissions).
</longdescription>
</pkgmetadata>
|
GitWeb
