https://bugzilla.novell.com/show_bug.cgi?id=866257 https://bugzilla.novell.com/show_bug.cgi?id=866257#c12 --- Comment #12 from Dominique Leuenberger <dimstar@opensuse.org> 2014-09-18 15:30:41 UTC --- (In reply to comment #11)
(In reply to comment #10)
g-s runs as user and does not have the needed permission to install meta-data to the required location (/usr/share/app-info)
Then g-s uses PackageKit? Why not using PK for refreshing the appdata?
g-s does... other similar software installers might or might not (appstream goes beyond PackageKit, see for example also listaller, using the same data set) Hence the actual goal to not only make PK work, but get a solution for the final thing. Additionally: if a user does zypper refresh, then PK uses the zypp internal refresh code and won't trigger refreshs anytime soon, thus putting a good risk that the meta data is different (and a forced refresh sounds like a performance penalty I'd like to avoid)
AFAIK zypp_refresh_cache is the location that loops over the 'interesting' repos and refreshes their metadata. After the loop all repos are up-to-date. Isn't this exactly where you want to update the appdata? This way g-s should see the same applications PK is able to deliver.
I will have another look here, to make sure we don't trigger this too often or risk of missing refreshes... but it will mean that any other tool might have to implement similar things to get such triggers to work too -- 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.