04.01.2017 19:17, Andrei Borzenkov пишет: ...
Yes, I do see some in "application" list.
cer@Telcontar:~> zypper se -t application Loading repository data... Reading installed packages...
S | Name | Summary | Type --+----------------------------------+-----------------------------------------------------+------------ i | AbiWord | Compose, edit, and view documents | application
i | VLC Media player | Read, capture, broadcast your multimedia streams | application i | VMware Player | Run a virtual machine | application <===
OK, you should be able to see what package corresponds to this Application with
zypper info --requires -t application 'VMware Player'
i | calibre | The one stop solution to all your e-book needs | application
This one likely comes from openSUSE
i | calibre - E-book Editor | Edit the text and styles inside e-books | application i | calibre - E-book Viewer | Read e-books in over a dozen different formats | application
...
Not really. Applications themselves are not "installed". Rather it is simply metadata that pulls in some "real" packages (RPMs). If you have those RPMs installed, it thinks Application is also there. Mostly the same mechanism as patches.
It could be that Applications cannot distinguish between packages coming from different repo. Not sure if it is technically possible.
I was wrong here. The presence of installed application is indicated by file in /usr/share/appdata (actually, it could also be /usr/share/metainfo as far as I can tell). Available applications are listed in appdata.xml.gz in each repository metadata. zypper cross links installed applications to repo using <id> tag found in both cases. Now, I also have "VMware Player" application because installing VMware player bundle apparently also adds files to /usr/share/appdata. If you can trace origin of other files in this directory (I mean, files that do not belong to any package) I think this is legitimate topic for discussion, because it means we cannot blindly assume presence of this file indicates presence of (openSUSE) application. Otherwise you can simply delete offending files. Note that zypper caches information (or, better, it builds solv files that are used internally) and I am not aware of any way to request solv cache rebuild for installed packages/applications. Reinstalling some package is workaround, as it should trigger cache rebuild. Removing /var/cache/zypp/solv/@System should recreate it next time too.