https://bugzilla.novell.com/show_bug.cgi?id=866257 https://bugzilla.novell.com/show_bug.cgi?id=866257#c3 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|dimstar@opensuse.org | --- Comment #3 from Dominique Leuenberger <dimstar@opensuse.org> 2014-09-09 20:12:32 UTC --- (In reply to comment #2)
@Dominique: Actually i don't like to have too much knowledge about the application details coded in libzypp. So I'd suggest to use a plugin for this. (http://doc.opensuse.org/projects/libzypp/HEAD/zypp-plugins.html)
- I'd provide a plugin hook within libzypp; called after a repos raw matadata were updated. Zypp could pass the path to the directory tree containing the new metadata and the repos type to the plugin.
- Some gnome package had to provide the plugin script picking and consuming the appdata.
Would that be ok?
I guess that would be fine. I would need hooks on: - Repo refresh (install new appdata into the right location) - Repo disable/enable (remove/install appdata) - Repo rename (uninstall old appdata/install new appdata) - Repo delete (uninstall appdata) I think that's about all the cases I would need to hook in. In any case I would need to know 'where' to find the raw cache data (/var/cache/zypp/raw/<reponame>, the 'repo type' (rpm-md has a repodata folder with all the content, while yast has the /suse/setup/descr structure) and the 'type' of action. The zypp hooks would be installed by gnome-software (or any package it depends on). -- 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.