[gnome-utils/gsettings-tutorial] [gsettings-tutorial] gschema-compile needs --allow-any-name

[Vincent Untz <vuntz src gnome org>]

commit 269c19766b8537803ae760ba9daa3582a3fb3eef
Author: Vincent Untz <vuntz gnome org>
Date:   Fri Apr 16 20:09:40 2010 -0400

    [gsettings-tutorial] gschema-compile needs --allow-any-name
    
    This is a temporary change: once the port to GSettings is complete and
    once it has been decided to stop using gconf, this should be removed to
    make sure the GSettings schema is following the best practices for key
    naming.

 baobab/data/Makefile.am |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
---
diff --git a/baobab/data/Makefile.am b/baobab/data/Makefile.am
index 54e2bf1..64e1ef0 100644
--- a/baobab/data/Makefile.am
+++ b/baobab/data/Makefile.am
@@ -19,8 +19,9 @@ schemas_DATA 	 = $(schemas_in_files:.schemas.in=.schemas)
 gsettingsschema_DATA = org.gnome.baobab.gschema
 org.gnome.baobab.gschema: baobab.schemas
 	gsettings-schema-convert --force --gconf --xml --schema-id $(@:.gschema=) $< -o $@
+# --allow-any-name should be removed once the move from gconf is complete
 install-data-hook:
-	$(gsettingsupdateschemacache) $(gsettingsschemadir)
+	$(gsettingsupdateschemacache) --allow-any-name $(gsettingsschemadir)
 
 man_MANS = baobab.1