Task #431
closed
Task #358: Better package our work
Use Gconftool command instead of Xml Gconf files
Added by Jean-Michel Philippe about 13 years ago.
Updated over 12 years ago.
Description
To reduce the need of configuration files in chroot_local-includes, we need to move user's settings in session startup scripts and use gconftool-2 instead of copying Xml files into $HOME/.gconf/. These scripts can then be provided by custom Debian packages. In some cases however, it will be simpler to use a default set of Xml files plus gconftool-2 calls to tune them to the user's language.
- Due date changed from 11/14/2011 to 02/20/2012
- Target version changed from 2011-11 to 2012-02
- Start date changed from 10/17/2011 to 01/09/2012
Although Gconf files have now moved to package ddl-activities and don't use space in chroot_local-includes anymore, using gconftool-2 is a better way to deal with smooth upgrade of user's data.
It seems anyway that a raw copy of a previously saved set of gconf files is not always working, supposedly because of time stamps they contain. In this case the copied files are cleaned up at first invocation of Gconftool by an application. We then need to use gconftool-2 commands for each entry to be set.
- Category changed from Packaging to Development
- Status changed from New to Ready for test
- % Done changed from 0 to 100
There is now a loop in the script creating user's account that get each gconf entry in source data and execute the corresponding gconftool-2 command. New Gconf params can then just be added to the .gconf/ directory of the target user.
- Status changed from Ready for test to Closed
Also available in: Atom
PDF
Updated by