1
<page xmlns="http://projectmallard.org/1.0/"
2
type="topic" style="task"
5
<revision version="0.1" date="2012-05-21" status="stub"/>
7
<credit type="author copyright">
8
<name>Michael Hill</name>
9
<email>mdhillca@gmail.com</email>
16
<title>Why shouldn't I use gsettings overrides?</title>
19
<cite date="2012-07-05" href="mailto:mdhillca@gmail.com">Michael Hill</cite>
20
<p>Adapted from d-g-o GSettings page. Add a see-also?</p>
23
<p>Gsettings overrides are used by distributions to adjust default settings
24
for the GNOME desktop and apps. dconf overrides were designed for system
25
administrators to adjust default settings and set mandatory settings for the
26
GNOME desktop and apps.</p>
28
<p>GNOME developers are working towards allowing or even requiring <file>/usr/</file>
29
to be mounted read-only with the exception of <file>/usr/local/</file>.</p>
32
<p>Default values are defined in the schemas that get installed by an
33
application. Sometimes, it is necessary for a vendor or distributor to adjust
34
these defaults. Since patching the XML source for the schema is inconvenient
35
and error-prone, glib-compile-schemas reads so-called
36
<em>"vendor override"</em> files. These are keyfiles in the same directory
37
as the XML schema sources which can override default values. The schema id
38
serves as the group name in the key file, and the values are expected in
39
serialized GVariant form, as in the following example:</p>
added
removed
system-admin-guide/C/overrides.page
