1TRACKER-XDG-PORTAL(1) Tracker manual TRACKER-XDG-PORTAL(1)
2
3
4
6 tracker-xdg-portal-3 - Portal to Tracker endpoints
7
9 tracker-xdg-portal-3 [--version | -v]
10
12 This daemon allows access to Tracker endpoints in a controlled manner.
13 By default access to every service is disallowed, services may be
14 whitelisted through additional policy in the .flatpak-info file.
15
16 When whitelisting services, the policy may define specific graph names
17 to allow access to, the default keyword to allow access to the default
18 unnamed graph, or * keyword to allow access to all graphs.
19
21 When interacting with sandboxed clients, the service expects the
22 following format in the .flatpak-info file:
23
24 [Policy Tracker3]
25 dbus:org.example.SparqlEndpoint1=graphA;graphB;default
26 dbus:org.example.SparqlEndpoint2=*
27
28 This will allow access to the endpoints behind the
29 org.example.SparqlEndpoint1 and org.example.SparqlEndpoint2 bus names.
30 Only to the graphA and graphB graph IRIs and the default unnamed graph
31 on the first endpoint, and to all graphs in the second.
32
33 This policy can be set when building or running the sandboxed
34 application through the --add-policy option. This can be set via
35 finish-args in the flatpak manifest, specified along the build chain in
36 flatpak-build-finish(1), or modified at start time with flatpak-run(1).
37 For example:
38
39 $ flatpak run \
40 --add-policy=Tracker3.dbus:org.example.SparqlEndpoint1=graphA \
41 --add-policy=Tracker3.dbus:org.example.SparqlEndpoint1=graphB \
42 --add-policy=Tracker3.dbus:org.example.SparqlEndpoint1=default \
43 --add-policy=Tracker3.dbus:org.example.SparqlEndpoint2=* \
44 org.freedesktop.TrackerSandbox
45
47 flatpak-build-finish(1), flatpak-override(1), flatpak-run(1)
48
49
50
51 3.6.0 09/19/2023 TRACKER-XDG-PORTAL(1)