The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #3137

Type for manipulating gconf

Added by Andrew Pollock over 4 years ago. Updated 10 months ago.

Status:AcceptedStart date:02/01/2010
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:newfeature
Target version:-
Affected Puppet version:development Branch:
Keywords:gconf

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket is now tracked at: https://tickets.puppetlabs.com/browse/PUP-1260


Description

Currently we’re managing GNOME mandatory policy by carting around a monolithic /etc/gconf/gconf.xml.mandatory/%gonf-tree.xml, which is a bit ghetto. It makes it difficult to have any granularity in what the mandatory policy contains.

I was thinking that it’d be cool if Puppet had gconf support directory, so in the DSL, you’d specify that you wanted something set, and it’d run gconftool for you, and make the necessary modifications

See also http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions#I.27m_a_systems_administrator.__How_can_I_set_policies_for_all_users_of_my_system.3F

History

#1 Updated by James Turnbull over 4 years ago

  • Category set to newfeature
  • Status changed from Unreviewed to Accepted
  • Target version set to 4

#2 Updated by James Turnbull about 3 years ago

  • Target version deleted (4)

#3 Updated by Anonymous 10 months ago

Redmine Issue #3137 has been migrated to JIRA:

https://tickets.puppetlabs.com/browse/PUP-1260

Also available in: Atom PDF