There should be always some restriction. All /etc/sysconfig is just sysconfigs, but permission to this files can be really various.
My idea is that inside of add/edit action you have something ( you have ruby, so various nice ways ) that map file to lense. And then you just pass map to augeas with given lense.
So in code of directory agent can be something like
lense = case file when /ifcfg-.*/ then "sysconfig.lense" when /scrips/ then "bash.lense" else raise "unsuported File" end
I haven't so much experience with ruby, so I thought about C++ like approach ;-) class SysconfigAgent < ConfigAgentService::FileService as a generic ancestor of agents accessing sysconfig files (so not binded to particular file) It can use already implemented API. Michal -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org