https://bugzilla.novell.com/show_bug.cgi?id=866257 https://bugzilla.novell.com/show_bug.cgi?id=866257#c13 --- Comment #13 from Michael Andres <ma@suse.com> 2014-09-19 14:53:54 CEST ---
Hence the actual goal to not only make PK work, but get a solution for the final thing.
So back to the python snippet? The python snippet 'knows' about the system repos and it can feed the 'final thing'. Without performing a refresh by itself, it could check and sync the latest apdata state into the 'final thing' quite fast if there's nothing todo (and without need to care about any zypp lock). A 'repo refresh' - if performed - just tells you that something in the repo changed. I assume the appdata in a repo change far less frequently than the repos package data. So updating the 'final thing' with each repo refresh is probably superfluous. The python snippet could remember size/md5 sum of the appdata files it already fed, and feed only changed stuff/add new/remove outdated. If nothing has changed, there's not much to do. You could think about putting it into /etc/cron.hourly and it will pick up the latest state once an hour... ...while I'm looking for a place in libzypp to trigger the script. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.