On Fri, Oct 12, 2007 at 01:35:24PM -0400, Justin Haygood wrote:
- The actual policies as defined by the system administrator is located in /etc/PolicyKit/PolicyKit.conf
Now my question is, how should I go about generating this file? Should we use this file directly, or use sysconfig to generate the file dynamically, and potentially provide for a "local include" so that you can include custom policies not set via YaST?
Well, this is a general question for any package - should we use sysconfig? http://en.opensuse.org/SUSE_Package_Conventions/Sysconfig says: "/etc/sysconfig/ is the central place for system configuration files for SUSE Linux. Generally, it includes setting that should be configurable but cannot be modified by native config files below /etc. It does not supply the native config files or duplicate information from such files." So I think that we should stick with the native config file. If it turns out to be too complex, then yes, I would separate it to a yast-managed part, which can have additional restrictions to make it manageable, and a human-jungle part, where the admin can exploit the full potential of the tool. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org