[yast-devel] New feature of infrastucture of yast++
Hi, I would like to inform, that infrastrucure for config agents have new feature. Agent frontend can ask what polkit permission it requires. So e.g. so can check it before it is needed or you can report which one is missing ( preparation for tool that can run YLib and only return needed permission to given task ). So how to use it? quite simple: require "config_agent/mkinitrd" ConfigAgent::Mkinitrd.polkit_permissions => {:execute => "org.opensuse.config_agent.script.mkinitrd.execute"} BTW what should be proper place to document such feature? Code is already documented via yard [0][1]? Josef [0] http://rubydoc.info/github/yast/yast--/DbusClients/FileClient#polkit_permiss... [1] http://rubydoc.info/github/yast/yast--/DbusClients/ScriptClient#polkit_permi... -- Josef Reidinger Software Engineer Appliance Department SUSE LINUX, s. r. o. Lihovarska 1060/12 190 00 Praha 9 Czech Republic jreidinger@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 22.2.2012 16:59, Josef Reidinger wrote:
Hi, ... quite simple: require "config_agent/mkinitrd" ConfigAgent::Mkinitrd.polkit_permissions => {:execute => "org.opensuse.config_agent.script.mkinitrd.execute"}
Thanks for the info.
BTW what should be proper place to document such feature? Code is already documented via yard [0][1]?
IMO the developer's guide might be a good idea https://github.com/yast/yast--/blob/master/doc/tutorial.txt Bye Lukas -- Lukas Ocilka, Appliances Department, SUSE LINUX s.r.o. MD: Jeff Hawn, Jennifer Guild, Alena Hendrichova -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 22.2.2012 17:28, Lukas Ocilka wrote:
On 22.2.2012 16:59, Josef Reidinger wrote:
BTW what should be proper place to document such feature? Code is already documented via yard [0][1]?
IMO the developer's guide might be a good idea https://github.com/yast/yast--/blob/master/doc/tutorial.txt
Also architecture.txt contains section "Defining Policies"... Lukas -- Lukas Ocilka, Appliances Department, SUSE LINUX s.r.o. MD: Jeff Hawn, Jennifer Guild, Alena Hendrichova -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Wed, 22 Feb 2012 17:30:47 +0100 Lukas Ocilka <lukas.ocilka@suse.cz> wrote:
On 22.2.2012 17:28, Lukas Ocilka wrote:
On 22.2.2012 16:59, Josef Reidinger wrote:
BTW what should be proper place to document such feature? Code is already documented via yard [0][1]?
IMO the developer's guide might be a good idea https://github.com/yast/yast--/blob/master/doc/tutorial.txt
Also architecture.txt contains section "Defining Policies"...
Lukas
Tutorial should be quick introduction how to write own agent, so it doesn't fit there. Architecture is quite good, so I add it there. and Maybe I should create some front page for parts of architecture ( frontend, backend and transportation layer, so it will be in generated page ). Josef -- Josef Reidinger Software Engineer Appliance Department SUSE LINUX, s. r. o. Lihovarska 1060/12 190 00 Praha 9 Czech Republic jreidinger@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (2)
-
Josef Reidinger -
Lukas Ocilka