On Wednesday 09 September 2009 10:36:34 Stefan Schubert wrote:
I think we should use only one way to support script calls, cause the SCR.execute call does already some security checks while calling scripts.
What security checks does SCR.execute do? Does it parse the script I want to call before it gets executed? Does it find out that my script does a "mail -s Test -a /etc/passwd"? What if it no script but a binary?
Who generates the zypper calls and for what it is used for. Currently the "package- communication-way" of WebYaST is PackageKit. Could we use it too ?
If I use the Perl script it would call zypper directly. Using the Perl module it would return a big hash with the changes that have to be done to the system. As I have to write a new wrapper script I could make it behave like the latter and let it dump the changes list. Changes to the system can be: - Add and remove services - Enable and disable catalogs (for each service) - Add and remove repositories Does PackageKit support this? Ciao, Daniel -- J. Daniel Schmidt <jdsn@suse.de> SUSE Linux Products GmbH Research & Development Maxfeldstr. 5 GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 Nürnberg -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org