![](https://seccdn.libravatar.org/avatar/654c5b4f0d657240edff9440a901839b.jpg?s=120&d=mm&r=g)
On 22.1.2010 16:01, Klaus Kaempf wrote: [...]
Uhm, is the set of attributes available for reading (alias, name, status) really different from writing (status, prio, refresh) ??
Yes, it is strange. I think that's because it is backend-dependent. The libzypp-backed can set refresh and priority in RepoSetData() (see http://www.packagekit.org/gtk-doc/Transaction.html#Transaction.RepoSetData) But this function is backend-dependant, the call has two generic arguments (called parameter and value) and it's completely up to the backend what it implements and how it behaves. Unfortunately there is no RepoGetData() call so it not possible to query for backend specific settings (in our case it is priority and autorefresh).
If PackageKit cannot be enhanced at reasonable costs, calling 'zypper' from a D-Bus service (implemented in Ruby) would be a better option IMHO.
Right, but I hope it won't be needed... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org