[nautilus-actions] No more obsolete reading of GConf after migration



commit e38ac184d05c7b000d3d6a4693f4a5bd5b463b85
Author: Pierre Wieser <pwieser trychlos org>
Date:   Fri Jun 10 20:39:13 2011 +0200

    No more obsolete reading of GConf after migration
    
    It may be needed to re-migrate a newly inserted item in GConf after a first successfull
    migration, we so keep GConf readable.

 ChangeLog                    |    3 +++
 src/utils/na-gconf2key.sh.in |    1 -
 2 files changed, 3 insertions(+), 1 deletions(-)
---
diff --git a/ChangeLog b/ChangeLog
index bdb9234..9d497b2 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,8 @@
 2011-06-10 Pierre Wieser <pwieser trychlos org>
 
+	* src/utils/na-gconf2key.sh.in: No more obsolete the GConf reading,
+	as it may sometimes be needed to re-migrate a newly inserted item.
+
 	* src/io-gconf/nagp-reader.c (get_boxed_from_path):
 	Only allocate a new box when a non-null value has been read.
 
diff --git a/src/utils/na-gconf2key.sh.in b/src/utils/na-gconf2key.sh.in
index f436f88..9665ed3 100644
--- a/src/utils/na-gconf2key.sh.in
+++ b/src/utils/na-gconf2key.sh.in
@@ -606,7 +606,6 @@ if [ $(id -u) -eq 0 ]; then
 	# as a security - while we are root -, we force the GConf i/o provider to be locked
 	cat <<! >${my_tmproot}.io-provider_na-gconf
 # Starting with 3.1.0, GConf as I/O provider is deprecated
-readable = false
 writable = false
 !
 fi



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]