|--==> Josselin Mouette writes: JM> Le jeudi 22 septembre 2005 à 08:35 +0100, Free Ekanayaka a écrit : >>Then, to populate the configuration source with the relevant >>%gconf.xml, I run: >> >>gconftool-2 --direct \ >>--config-source xml:readwrite:/usr/share/gconf/cdd.defaults \ >>--load my.entries
JM> I don't know who had the idea to populate a directory in /usr this way, JM> but he got it all wrong. I completely misunderstood the way you were JM> populating gconf entries, and it is *very* wrong. You shouldn't do that JM> in /usr. Well, the idea came from the Gnome Administration Guide: http://www.gnome.org/learn/admin-guide/latest/ch01s05.html and http://www.gnome.org/learn/admin-guide/latest/ch01s06.html Let me also add that I'm not populating /usr *directly*, what I actually do is to issue the command in the debian/rules file of debian package, which in turns installs the %gconf files under /usr. See: http://demudi.agnula.org/file/packages/cdd/debian/rules JM> We're currently discussing it on IRC. We'll have to come up with a JM> correct framework for CDD distributions, as it seems everyone got it all JM> wrong. That's good. JM> In the end, we'll try to keep it simple, but one things is sure: JM> you'll have to change the way you are doing things. Just don't use what JM> was done in gconf2 2.10.1-2, it's simply not suitable for this kind of JM> needs. Ok, I've no problem in changing, please just let me know when you end up to a satisfactory solution. Cheers, Free
