[yast-devel] WebYaST - Repository manager
Hi, I have a question regarding the Repository manager feature. I found that PackageKit doesn't support all needed actions for this feature: Only alias, name, status (enabled/disabled) can be read, AFAIK there is no way to read url, keep_packages, autorefresh and priority attributes. Similar problem is with writing, only status, priority and autorefresh can be changed. It seems that we need to enhance PackageKit and libzypp-backend, or have I overlooked something? Or should we use another backend in the Repository manager (e.g. pkg-bindings)? -- 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
* Ladislav Slezak <lslezak@suse.cz> [Jan 22. 2010 15:51]:
Hi,
I have a question regarding the Repository manager feature.
I found that PackageKit doesn't support all needed actions for this feature:
Only alias, name, status (enabled/disabled) can be read, AFAIK there is no way to read url, keep_packages, autorefresh and priority attributes.
Similar problem is with writing, only status, priority and autorefresh can be changed.
Uhm, is the set of attributes available for reading (alias, name, status) really different from writing (status, prio, refresh) ??
It seems that we need to enhance PackageKit and libzypp-backend, or have I overlooked something?
I'd prefer this, if it has reasonable effort and we can push the changes upstream.
Or should we use another backend in the Repository manager (e.g. pkg-bindings)?
If PackageKit cannot be enhanced at reasonable costs, calling 'zypper' from a D-Bus service (implemented in Ruby) would be a better option IMHO. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
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
participants (2)
-
Klaus Kaempf -
Ladislav Slezak