Linked by Thom Holwerda on Fri 21st Mar 2008 21:49 UTC
Permalink for comment 306241
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2005-07-13
I use gconftool-2 scripts. But for larger chunks of config, I believe you can --dump particular branches of gconf to xml and then load them to various accounts. For example:
gconftool-2 --dump /apps/evolution > evolution.xml
gconftool-2 --load=evolution.xml
Or say you just wanted calendar settings:
gconftool-2 --dump /apps/evolution/calendar > calendar.xml
Copying around config files sounds like something out of the DOS dark ages.
You're arguing that gconftool is somehow slicker than cp .kde/share/config/whatever destination. Different strokes for different folks.
In fact, to be pedantic, if you're administering multiple clients, then KDE's Kiosk infrastructure is optimized for that, and has been for some time. That's why the config file structure is set up the way it is. It has a hierarchy that gives you the adminstrator granular control over the user setup, and application configurations, and the extent that they can change it.
I guess it's the difference between copying chunks of gfconf settings and pasting them into multiple accounts, or simply setting up one or more profiles and applying it to multiple accounts. Again, different strokes.