Feature changed by: Ladislav Slezák (lslezak) Feature #319035, revision 4 Title: Make YaST (incl. modules) available in GNOME Software openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Dominique Leuenberger (dimstar) Partner organization: openSUSE.org Description: GNOME Software is an other way of handling installations. Instead of being package centric, it is application centric. An application is being represented by means of an appdata.xml file in it's setup (installed to /usr/share/appdata), then a metadata parser extracts this info and produces 'AppStream' metadata (to be consumed by software centers) In order to make extensions/plugins to applications discoverable, a package can add a metainfo.xml file to the same location and have itself listed as an extension/addon to the application. For YaST, this results in: - an appdata.xml file being provided together with YaST.desktop (done) - For all yast modules to install a metainfo.xml file, describin their extensive nature to yast. Relations: - metainfo.xml file format definition (url: http://www.freedesktop.org/software/appstream/docs/sect-Metadata-Addon.html) Discussion: #1: Ladislav Slezak (lslezak) (2015-05-27 10:39:22) The metainfo.xml file should be generated from *.spec file at build time, basically all values can be copied from there. Creating the files manually does not make much sense and they would get out of sync quite easily... + #2: Ladislav Slezák (lslezak) (2018-11-15 14:32:46) + Some details I got from Dominique: + * Example file for the main YaST application: https://github.com/DimStar77/openSUSE-appstream/blob/master/appdata-extra/de... + (https://github.com/DimStar77/openSUSE-appstream/blob/master/appdata-extra/de...) + * The YaST modules should define an extension for it (like plugins for + the base application), examples: https://github.com/DimStar77/openSUSE-appstream/tree/master/appdata-extra/me... + (https://github.com/DimStar77/openSUSE-appstream/tree/master/appdata-extra/me...) + * The XML files can be validated with "appstream-util validate FOO. + metainfo.xml" command (from the appstream-glib package) + * The metadata are also used by https://software.opensuse.org + (https://software.opensuse.org) , the main appdata XML for yast2.rpm + would be displayed at the https://software.opensuse.org/package/yast2 + (https://software.opensuse.org/package/yast2) page, i.e. there is also + a use case outside the GNOME Software package -- openSUSE Feature: https://features.opensuse.org/319035

Feature changed by: Mindaugas Baranauskas (embar-) Feature #319035, revision 6 Title: Make YaST (incl. modules) available in GNOME Software openSUSE Distribution: Done Priority Requester: Desirable Requested by: Dominique Leuenberger (dimstar) Partner organization: openSUSE.org Description: GNOME Software is an other way of handling installations. Instead of being package centric, it is application centric. An application is being represented by means of an appdata.xml file in it's setup (installed to /usr/share/appdata), then a metadata parser extracts this info and produces 'AppStream' metadata (to be consumed by software centers) In order to make extensions/plugins to applications discoverable, a package can add a metainfo.xml file to the same location and have itself listed as an extension/addon to the application. For YaST, this results in: - an appdata.xml file being provided together with YaST.desktop (done) - For all yast modules to install a metainfo.xml file, describin their extensive nature to yast. Relations: - metainfo.xml file format definition (url: http://www.freedesktop.org/software/appstream/docs/sect-Metadata-Addon.html) Discussion: #1: Ladislav Slezak (lslezak) (2015-05-27 10:39:22) The metainfo.xml file should be generated from *.spec file at build time, basically all values can be copied from there. Creating the files manually does not make much sense and they would get out of sync quite easily... #2: Ladislav Slezák (lslezak) (2018-11-15 14:32:46) Some details I got from Dominique: * Example file for the main YaST application: https://github.com/DimStar77/openSUSE-appstream/blob/master/appdata-extra/de... (https://github.com/DimStar77/openSUSE-appstream/blob/master/appdata-extra/de...) * The YaST modules should define an extension for it (like plugins for the base application), examples: https://github.com/DimStar77/openSUSE-appstream/tree/master/appdata-extra/me... (https://github.com/DimStar77/openSUSE-appstream/tree/master/appdata-extra/me...) * The XML files can be validated with "appstream-util validate FOO. metainfo.xml" command (from the appstream-glib package) * The metadata are also used by https://software.opensuse.org (https://software.opensuse.org) , the main appdata XML for yast2.rpm would be displayed at the https://software.opensuse.org/package/yast2 (https://software.opensuse.org/package/yast2) page, i.e. there is also a use case outside the GNOME Software package #3: Ladislav Slezák (lslezak) (2019-06-17 07:10:56) Thanks to Stasiek (lcp) the metadata have been added to all YaST packages, see https://github.com/yast/yast-yast2/issues/934 (https://github.com/yast/yast-yast2/issues/934) . The changes have been submitted to the openSUSE Tumbleweed and will be also available in the openSUSE Leap 15.2. Closing as DONE. + #4: Mindaugas Baranauskas (embar-) (2019-12-22 06:30:53) + Relevant changes introduced bug in YaST: + https://bugzilla.suse.com/show_bug.cgi?id=1158708 -- openSUSE Feature: https://features.opensuse.org/319035