[glib] man pages: document the order of schema overrides
- From: Ryan Lortie <ryanl src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [glib] man pages: document the order of schema overrides
- Date: Sat, 17 Mar 2012 16:41:46 +0000 (UTC)
commit 1b08ad61cdd19899f51ec44242913b18576861e1
Author: Ryan Lortie <desrt desrt ca>
Date: Sat Mar 17 12:39:23 2012 -0400
man pages: document the order of schema overrides
GSettings overrides are processed in such a way that
alphabetically-later files have precedence over earlier files (eg: 20_
will beat 10_). Document that fact.
docs/reference/gio/glib-compile-schemas.xml | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
---
diff --git a/docs/reference/gio/glib-compile-schemas.xml b/docs/reference/gio/glib-compile-schemas.xml
index 9055355..65236d4 100644
--- a/docs/reference/gio/glib-compile-schemas.xml
+++ b/docs/reference/gio/glib-compile-schemas.xml
@@ -43,6 +43,13 @@ values are written in serialized GVariant form.
Vendor ovrride files must have the filename extension
<filename>.gschema.override</filename>.
</para>
+<para>
+By convention, vendor override files begin with <filename>nn_</filename>
+where <filename>nn</filename> is a number from 00 to 99. Higher
+numbered files have higher priority (eg: if the same override is made in
+a file numbered 10 and then again in a file numbered 20, the override
+from 20 will take precedence).
+</para>
<refsect2><title>Options</title>
<variablelist>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]