appstream listaller
play

AppStream & Listaller Matthias Klumpp mak@debian.org - PowerPoint PPT Presentation

Feb 19, 2024 •204 likes •1.66k views

The Problem AppStream Listaller Conclusion AppStream & Listaller Matthias Klumpp mak@debian.org matthias@tenstral.net February 2014 The Problem AppStream Listaller Conclusion Who am I? PackageKit Developer Debian Developer

  1. The Problem AppStream Listaller Conclusion What is wrong with application distribution? PPAs/Repositories are insecure: 3rd-party applications are installed with root permission, may override system components, break distribution upgrades, ... Handling of PPAs is not very simple for users PPAs are distribution-specific: Many 3rd-party apps are available for e.g. Ubuntu, while other distributions need their own repos PPAs have a complex structure and are an overkill if people just want to distribute an app on Linux Binary installers don’t integrate well and are difficult to handle. If executed as root, they are a potential security risk We need a simple and secure cross-desktop solution to install 3rd-party applications, which integrates well with the rest of the system

  2. The Problem AppStream Listaller Conclusion Two independent projects AppStream Cross-distro specifications for building software-center applications Metadata / database specs for distributors Some (optional) new metadata for upstream projects Interactive features (Ratings & Reviews, ...) Listaller Generates cross-distro application packages Tools for app developers to make their app work on many distros Additional specs to enhance “component metadata” in distributions Optional component, requires PackageKit (and ideally AppStream) to work

  3. The Problem AppStream Listaller Conclusion Two independent projects AppStream Cross-distro specifications for building software-center applications Metadata / database specs for distributors Some (optional) new metadata for upstream projects Interactive features (Ratings & Reviews, ...) Listaller Generates cross-distro application packages Tools for app developers to make their app work on many distros Additional specs to enhance “component metadata” in distributions Optional component, requires PackageKit (and ideally AppStream) to work

  4. The Problem AppStream Listaller Conclusion Two independent projects AppStream Cross-distro specifications for building software-center applications Metadata / database specs for distributors Some (optional) new metadata for upstream projects Interactive features (Ratings & Reviews, ...) Listaller Generates cross-distro application packages Tools for app developers to make their app work on many distros Additional specs to enhance “component metadata” in distributions Optional component, requires PackageKit (and ideally AppStream) to work

  5. The Problem AppStream Listaller Conclusion Two independent projects AppStream Cross-distro specifications for building software-center applications Metadata / database specs for distributors Some (optional) new metadata for upstream projects Interactive features (Ratings & Reviews, ...) Listaller Generates cross-distro application packages Tools for app developers to make their app work on many distros Additional specs to enhance “component metadata” in distributions Optional component, requires PackageKit (and ideally AppStream) to work

  6. The Problem AppStream Listaller Conclusion Two independent projects AppStream Cross-distro specifications for building software-center applications Metadata / database specs for distributors Some (optional) new metadata for upstream projects Interactive features (Ratings & Reviews, ...) Listaller Generates cross-distro application packages Tools for app developers to make their app work on many distros Additional specs to enhance “component metadata” in distributions Optional component, requires PackageKit (and ideally AppStream) to work

  7. The Problem AppStream Listaller Conclusion Two independent projects AppStream Cross-distro specifications for building software-center applications Metadata / database specs for distributors Some (optional) new metadata for upstream projects Interactive features (Ratings & Reviews, ...) Listaller Generates cross-distro application packages Tools for app developers to make their app work on many distros Additional specs to enhance “component metadata” in distributions Optional component, requires PackageKit (and ideally AppStream) to work

  8. The Problem AppStream Listaller Conclusion Two independent projects AppStream Cross-distro specifications for building software-center applications Metadata / database specs for distributors Some (optional) new metadata for upstream projects Interactive features (Ratings & Reviews, ...) Listaller Generates cross-distro application packages Tools for app developers to make their app work on many distros Additional specs to enhance “component metadata” in distributions Optional component, requires PackageKit (and ideally AppStream) to work

  9. The Problem AppStream Listaller Conclusion Two independent projects AppStream Cross-distro specifications for building software-center applications Metadata / database specs for distributors Some (optional) new metadata for upstream projects Interactive features (Ratings & Reviews, ...) Listaller Generates cross-distro application packages Tools for app developers to make their app work on many distros Additional specs to enhance “component metadata” in distributions Optional component, requires PackageKit (and ideally AppStream) to work

  10. The Problem AppStream Listaller Conclusion AppInstaller meeting 2011 Fedora, Debian, OpenSUSE, Mageia, Ubuntu, KDE, Freedesktop

  11. The Problem AppStream Listaller Conclusion AppStream Concept

  12. The Problem AppStream Listaller Conclusion AppStream Concept

  13. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  14. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  15. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  16. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  17. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, icon, XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  18. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, icon, author data, XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  19. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, icon, author data, project group, XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  20. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, icon, author data, project group, categories, XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  21. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, icon, author data, project group, categories, mimetypes, XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  22. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, icon, author data, project group, categories, mimetypes, keywords, XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  23. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, icon, author data, project group, categories, mimetypes, keywords, screenshot references and descriptions, XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  24. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, icon, author data, project group, categories, mimetypes, keywords, screenshot references and descriptions, etc. XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  25. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, icon, author data, project group, categories, mimetypes, keywords, screenshot references and descriptions, etc. It also allows localization of some data XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  26. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, icon, author data, project group, categories, mimetypes, keywords, screenshot references and descriptions, etc. It also allows localization of some data XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  27. The Problem AppStream Listaller Conclusion AppStream XML AppStream XML contains meta-data for each application, such as name, unique app-id (desktop file), summary, description, icon, author data, project group, categories, mimetypes, keywords, screenshot references and descriptions, etc. It also allows localization of some data XML!? Debian FTP-Masters prefer YAML, adding XML to the metadata set is discouraged. A more general solution is wanted too. Problem Where do we get the data from if the distribution does not have it already in it’s package metadata or it is missing from desktop-files? Where do we get good screenshots from?

  28. The Problem AppStream Listaller Conclusion AppData Small XML file shipped with upstream project Subset of the AppStream XML specification Contains screenshot URLs to 3rd-party servers Is localized upstream No requirement to implement AppStream! It is just additional metadata to extend or improve existing data We would like to have upstreams ship the file to improve the quality of data which is used to present apps in a software center External content (like screenshots) is cached and verified on the distribution’s server

  29. The Problem AppStream Listaller Conclusion AppData Small XML file shipped with upstream project Subset of the AppStream XML specification Contains screenshot URLs to 3rd-party servers Is localized upstream No requirement to implement AppStream! It is just additional metadata to extend or improve existing data We would like to have upstreams ship the file to improve the quality of data which is used to present apps in a software center External content (like screenshots) is cached and verified on the distribution’s server

  30. The Problem AppStream Listaller Conclusion AppData Small XML file shipped with upstream project Subset of the AppStream XML specification Contains screenshot URLs to 3rd-party servers Is localized upstream No requirement to implement AppStream! It is just additional metadata to extend or improve existing data We would like to have upstreams ship the file to improve the quality of data which is used to present apps in a software center External content (like screenshots) is cached and verified on the distribution’s server

  31. The Problem AppStream Listaller Conclusion AppData Small XML file shipped with upstream project Subset of the AppStream XML specification Contains screenshot URLs to 3rd-party servers Is localized upstream No requirement to implement AppStream! It is just additional metadata to extend or improve existing data We would like to have upstreams ship the file to improve the quality of data which is used to present apps in a software center External content (like screenshots) is cached and verified on the distribution’s server

  32. The Problem AppStream Listaller Conclusion AppData Small XML file shipped with upstream project Subset of the AppStream XML specification Contains screenshot URLs to 3rd-party servers Is localized upstream No requirement to implement AppStream! It is just additional metadata to extend or improve existing data We would like to have upstreams ship the file to improve the quality of data which is used to present apps in a software center External content (like screenshots) is cached and verified on the distribution’s server

  33. The Problem AppStream Listaller Conclusion AppData Small XML file shipped with upstream project Subset of the AppStream XML specification Contains screenshot URLs to 3rd-party servers Is localized upstream No requirement to implement AppStream! It is just additional metadata to extend or improve existing data We would like to have upstreams ship the file to improve the quality of data which is used to present apps in a software center External content (like screenshots) is cached and verified on the distribution’s server

  34. The Problem AppStream Listaller Conclusion AppData Small XML file shipped with upstream project Subset of the AppStream XML specification Contains screenshot URLs to 3rd-party servers Is localized upstream No requirement to implement AppStream! It is just additional metadata to extend or improve existing data We would like to have upstreams ship the file to improve the quality of data which is used to present apps in a software center External content (like screenshots) is cached and verified on the distribution’s server

  35. The Problem AppStream Listaller Conclusion Some metadata statistics Fedora ships AppStream since v20 Applications in Fedora with: Long descriptions: 170 (9%) Keywords: 95 (5%) Categories: 1744 (98%) Screenshots: 143 (8%) GNOME applications with AppData: 60 (50%) KDE applications with AppData: 1 (1%) XFCE applications with AppData: 0 (0%) http://alt.fedoraproject.org/pub/alt/screenshots/f20/status.html

  36. The Problem AppStream Listaller Conclusion Some metadata statistics Fedora ships AppStream since v20 Applications in Fedora with: Long descriptions: 170 (9%) Keywords: 95 (5%) Categories: 1744 (98%) Screenshots: 143 (8%) GNOME applications with AppData: 60 (50%) KDE applications with AppData: 1 (1%) XFCE applications with AppData: 0 (0%) http://alt.fedoraproject.org/pub/alt/screenshots/f20/status.html

  37. The Problem AppStream Listaller Conclusion Some metadata statistics Fedora ships AppStream since v20 Applications in Fedora with: Long descriptions: 170 (9%) Keywords: 95 (5%) Categories: 1744 (98%) Screenshots: 143 (8%) GNOME applications with AppData: 60 (50%) KDE applications with AppData: 1 (1%) XFCE applications with AppData: 0 (0%) http://alt.fedoraproject.org/pub/alt/screenshots/f20/status.html

  38. The Problem AppStream Listaller Conclusion Some metadata statistics Fedora ships AppStream since v20 Applications in Fedora with: Long descriptions: 170 (9%) Keywords: 95 (5%) Categories: 1744 (98%) Screenshots: 143 (8%) GNOME applications with AppData: 60 (50%) KDE applications with AppData: 1 (1%) XFCE applications with AppData: 0 (0%) http://alt.fedoraproject.org/pub/alt/screenshots/f20/status.html

  39. The Problem AppStream Listaller Conclusion Some metadata statistics Fedora ships AppStream since v20 Applications in Fedora with: Long descriptions: 170 (9%) Keywords: 95 (5%) Categories: 1744 (98%) Screenshots: 143 (8%) GNOME applications with AppData: 60 (50%) KDE applications with AppData: 1 (1%) XFCE applications with AppData: 0 (0%) http://alt.fedoraproject.org/pub/alt/screenshots/f20/status.html

  40. The Problem AppStream Listaller Conclusion Some metadata statistics Fedora ships AppStream since v20 Applications in Fedora with: Long descriptions: 170 (9%) Keywords: 95 (5%) Categories: 1744 (98%) Screenshots: 143 (8%) GNOME applications with AppData: 60 (50%) KDE applications with AppData: 1 (1%) XFCE applications with AppData: 0 (0%) http://alt.fedoraproject.org/pub/alt/screenshots/f20/status.html

  41. The Problem AppStream Listaller Conclusion Some metadata statistics Fedora ships AppStream since v20 Applications in Fedora with: Long descriptions: 170 (9%) Keywords: 95 (5%) Categories: 1744 (98%) Screenshots: 143 (8%) GNOME applications with AppData: 60 (50%) KDE applications with AppData: 1 (1%) XFCE applications with AppData: 0 (0%) http://alt.fedoraproject.org/pub/alt/screenshots/f20/status.html

  42. The Problem AppStream Listaller Conclusion One database to rule them all In order to make use of AppStream, you have to combine many data sources (and consider fallback solutions) Debian will provide AppStream data in YAML (describing not only applications, but providing extra archive metadata), Ubuntu uses an own desktop-file extension, others use XML The AppStream software and libappstream were created to avoid to require every software center to provide parsers to all formats A Xapian database is generated, containing all data for software centers to access libappstream allows acessing the database and various other data sources using a GObject-based API (you don’t have to work with Xapian’s C++ interface)

  43. The Problem AppStream Listaller Conclusion One database to rule them all In order to make use of AppStream, you have to combine many data sources (and consider fallback solutions) Debian will provide AppStream data in YAML (describing not only applications, but providing extra archive metadata), Ubuntu uses an own desktop-file extension, others use XML The AppStream software and libappstream were created to avoid to require every software center to provide parsers to all formats A Xapian database is generated, containing all data for software centers to access libappstream allows acessing the database and various other data sources using a GObject-based API (you don’t have to work with Xapian’s C++ interface)

  44. The Problem AppStream Listaller Conclusion One database to rule them all In order to make use of AppStream, you have to combine many data sources (and consider fallback solutions) Debian will provide AppStream data in YAML (describing not only applications, but providing extra archive metadata), Ubuntu uses an own desktop-file extension, others use XML The AppStream software and libappstream were created to avoid to require every software center to provide parsers to all formats A Xapian database is generated, containing all data for software centers to access libappstream allows acessing the database and various other data sources using a GObject-based API (you don’t have to work with Xapian’s C++ interface)

  45. The Problem AppStream Listaller Conclusion One database to rule them all In order to make use of AppStream, you have to combine many data sources (and consider fallback solutions) Debian will provide AppStream data in YAML (describing not only applications, but providing extra archive metadata), Ubuntu uses an own desktop-file extension, others use XML The AppStream software and libappstream were created to avoid to require every software center to provide parsers to all formats A Xapian database is generated, containing all data for software centers to access libappstream allows acessing the database and various other data sources using a GObject-based API (you don’t have to work with Xapian’s C++ interface)

  46. The Problem AppStream Listaller Conclusion One database to rule them all In order to make use of AppStream, you have to combine many data sources (and consider fallback solutions) Debian will provide AppStream data in YAML (describing not only applications, but providing extra archive metadata), Ubuntu uses an own desktop-file extension, others use XML The AppStream software and libappstream were created to avoid to require every software center to provide parsers to all formats A Xapian database is generated, containing all data for software centers to access libappstream allows acessing the database and various other data sources using a GObject-based API (you don’t have to work with Xapian’s C++ interface)

  47. The Problem AppStream Listaller Conclusion One database to rule them all

  48. The Problem AppStream Listaller Conclusion GNOME? - AppStream status in desktops and distros GNOME-Software: Implementation of an AppStream-compatible software-center by the GNOME project Fully supported on Fedora, pending on other distributions, blocked on Debian by DEP-11 implementation

  49. The Problem AppStream Listaller Conclusion GNOME? - AppStream status in desktops and distros GNOME-Software: Implementation of an AppStream-compatible software-center by the GNOME project Fully supported on Fedora, pending on other distributions, blocked on Debian by DEP-11 implementation

  50. The Problem AppStream Listaller Conclusion KDE? - AppStream status in desktops and distros Apper: Initial support for AppStream via libappstream, needs work AppData inclusion into KDE projects is currently discussed Possible port of Muon Discover to PackageKit and AppStream

  51. The Problem AppStream Listaller Conclusion KDE? - AppStream status in desktops and distros Apper: Initial support for AppStream via libappstream, needs work AppData inclusion into KDE projects is currently discussed Possible port of Muon Discover to PackageKit and AppStream

  52. The Problem AppStream Listaller Conclusion KDE? - AppStream status in desktops and distros Apper: Initial support for AppStream via libappstream, needs work AppData inclusion into KDE projects is currently discussed Possible port of Muon Discover to PackageKit and AppStream

  53. The Problem AppStream Listaller Conclusion AppStream status in desktops and distros Debian: Work on the universal component-metadata file (defined as DEP-11) has started Ubuntu: Ships AppInstall, which can be consumed by libappstream, but will likely migrate to Debian’s solution Fedora: Ships AppStream XML and GNOME-Software, already supports screenshots OpenSUSE: Works on AppStream XML, work finished? So far, only GNOME has a software-center which fully supports almost everything from the AppStream specification

  54. The Problem AppStream Listaller Conclusion AppStream status in desktops and distros Debian: Work on the universal component-metadata file (defined as DEP-11) has started Ubuntu: Ships AppInstall, which can be consumed by libappstream, but will likely migrate to Debian’s solution Fedora: Ships AppStream XML and GNOME-Software, already supports screenshots OpenSUSE: Works on AppStream XML, work finished? So far, only GNOME has a software-center which fully supports almost everything from the AppStream specification

  55. The Problem AppStream Listaller Conclusion AppStream status in desktops and distros Debian: Work on the universal component-metadata file (defined as DEP-11) has started Ubuntu: Ships AppInstall, which can be consumed by libappstream, but will likely migrate to Debian’s solution Fedora: Ships AppStream XML and GNOME-Software, already supports screenshots OpenSUSE: Works on AppStream XML, work finished? So far, only GNOME has a software-center which fully supports almost everything from the AppStream specification

  56. The Problem AppStream Listaller Conclusion AppStream status in desktops and distros Debian: Work on the universal component-metadata file (defined as DEP-11) has started Ubuntu: Ships AppInstall, which can be consumed by libappstream, but will likely migrate to Debian’s solution Fedora: Ships AppStream XML and GNOME-Software, already supports screenshots OpenSUSE: Works on AppStream XML, work finished? So far, only GNOME has a software-center which fully supports almost everything from the AppStream specification

  57. The Problem AppStream Listaller Conclusion AppStream status in desktops and distros Debian: Work on the universal component-metadata file (defined as DEP-11) has started Ubuntu: Ships AppInstall, which can be consumed by libappstream, but will likely migrate to Debian’s solution Fedora: Ships AppStream XML and GNOME-Software, already supports screenshots OpenSUSE: Works on AppStream XML, work finished? So far, only GNOME has a software-center which fully supports almost everything from the AppStream specification

  58. The Problem AppStream Listaller Conclusion Listaller? Listaller is a complete solution for packaging and distributing 3rd-party applications. It provides tools for building cross-distro applications, creating and signing packages, update management and related features. It is completely invisible to the user on any system using PackageKit. Started in 2008 as an experiment Covered features of PackageKit and AppStream Switched to PackageKit in 2009 Merged with Autopackage and some other projects in 2010 AppStream was started in 2011, in turn Listaller was rewritten from scratch, dropping duplicate functionality Rewrite finished in 2012, many new concepts were implemented in 2013

  59. The Problem AppStream Listaller Conclusion Listaller? Listaller is a complete solution for packaging and distributing 3rd-party applications. It provides tools for building cross-distro applications, creating and signing packages, update management and related features. It is completely invisible to the user on any system using PackageKit. Started in 2008 as an experiment Covered features of PackageKit and AppStream Switched to PackageKit in 2009 Merged with Autopackage and some other projects in 2010 AppStream was started in 2011, in turn Listaller was rewritten from scratch, dropping duplicate functionality Rewrite finished in 2012, many new concepts were implemented in 2013

  60. The Problem AppStream Listaller Conclusion Listaller? Listaller is a complete solution for packaging and distributing 3rd-party applications. It provides tools for building cross-distro applications, creating and signing packages, update management and related features. It is completely invisible to the user on any system using PackageKit. Started in 2008 as an experiment Covered features of PackageKit and AppStream Switched to PackageKit in 2009 Merged with Autopackage and some other projects in 2010 AppStream was started in 2011, in turn Listaller was rewritten from scratch, dropping duplicate functionality Rewrite finished in 2012, many new concepts were implemented in 2013

  61. The Problem AppStream Listaller Conclusion Listaller? Listaller is a complete solution for packaging and distributing 3rd-party applications. It provides tools for building cross-distro applications, creating and signing packages, update management and related features. It is completely invisible to the user on any system using PackageKit. Started in 2008 as an experiment Covered features of PackageKit and AppStream Switched to PackageKit in 2009 Merged with Autopackage and some other projects in 2010 AppStream was started in 2011, in turn Listaller was rewritten from scratch, dropping duplicate functionality Rewrite finished in 2012, many new concepts were implemented in 2013

  62. The Problem AppStream Listaller Conclusion Listaller? Listaller is a complete solution for packaging and distributing 3rd-party applications. It provides tools for building cross-distro applications, creating and signing packages, update management and related features. It is completely invisible to the user on any system using PackageKit. Started in 2008 as an experiment Covered features of PackageKit and AppStream Switched to PackageKit in 2009 Merged with Autopackage and some other projects in 2010 AppStream was started in 2011, in turn Listaller was rewritten from scratch, dropping duplicate functionality Rewrite finished in 2012, many new concepts were implemented in 2013

  63. The Problem AppStream Listaller Conclusion Listaller? Listaller is a complete solution for packaging and distributing 3rd-party applications. It provides tools for building cross-distro applications, creating and signing packages, update management and related features. It is completely invisible to the user on any system using PackageKit. Started in 2008 as an experiment Covered features of PackageKit and AppStream Switched to PackageKit in 2009 Merged with Autopackage and some other projects in 2010 AppStream was started in 2011, in turn Listaller was rewritten from scratch, dropping duplicate functionality Rewrite finished in 2012, many new concepts were implemented in 2013

  64. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  65. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  66. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  67. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  68. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  69. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  70. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  71. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  72. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  73. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  74. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  75. The Problem AppStream Listaller Conclusion Goals System integration Users should not notice that Listaller is used when installing apps Software updates should be retrieved using the same UI as the system itself Listaller apps should integrate seamlessly with the system Cross-distro and -desktop compatibility Simplification No catch-all solution, Listaller should cover the most common use-cases. Native distribution packages should cover the remaining cases. Security Signatures, security hints database, sandboxing, ... Developer tools Provide helpers for developers to make their apps run on multiple distributions Make packaging as simple as possible, do some QA on the packaged app

  76. The Problem AppStream Listaller Conclusion Basic concept Listaller contains a PackageKit plugin, mediating between Listaller and PackageKit The plugin acts as »meta-backend«, sending information about Listaller packages via PackageKit’s DBus interface, and making queries to the native backend Every PackageKit client can install, remove and update Listaller packages Listaller installs some XML for AppStream-compatible software centers, so they can display details about a 3rd-party application Uses a superset of the AppData specification as source for application metadata

  77. The Problem AppStream Listaller Conclusion Basic concept Listaller contains a PackageKit plugin, mediating between Listaller and PackageKit The plugin acts as »meta-backend«, sending information about Listaller packages via PackageKit’s DBus interface, and making queries to the native backend Every PackageKit client can install, remove and update Listaller packages Listaller installs some XML for AppStream-compatible software centers, so they can display details about a 3rd-party application Uses a superset of the AppData specification as source for application metadata

  78. The Problem AppStream Listaller Conclusion Basic concept Listaller contains a PackageKit plugin, mediating between Listaller and PackageKit The plugin acts as »meta-backend«, sending information about Listaller packages via PackageKit’s DBus interface, and making queries to the native backend Every PackageKit client can install, remove and update Listaller packages Listaller installs some XML for AppStream-compatible software centers, so they can display details about a 3rd-party application Uses a superset of the AppData specification as source for application metadata

  79. The Problem AppStream Listaller Conclusion Basic concept Listaller contains a PackageKit plugin, mediating between Listaller and PackageKit The plugin acts as »meta-backend«, sending information about Listaller packages via PackageKit’s DBus interface, and making queries to the native backend Every PackageKit client can install, remove and update Listaller packages Listaller installs some XML for AppStream-compatible software centers, so they can display details about a 3rd-party application Uses a superset of the AppData specification as source for application metadata

  80. The Problem AppStream Listaller Conclusion Basic concept Listaller contains a PackageKit plugin, mediating between Listaller and PackageKit The plugin acts as »meta-backend«, sending information about Listaller packages via PackageKit’s DBus interface, and making queries to the native backend Every PackageKit client can install, remove and update Listaller packages Listaller installs some XML for AppStream-compatible software centers, so they can display details about a 3rd-party application Uses a superset of the AppData specification as source for application metadata

  81. The Problem AppStream Listaller Conclusion Listaller Tools

  82. The Problem AppStream Listaller Conclusion Utopia package creation 1 Write AppStream AppData describing the application 2 Write a small pkoptions file, defining few basic options for the package 3 Write a file/dir listing for the new package 4 Build the package! Listaller will use appcompile to determine the buildsystem and build the app, install it to a temporary location and then add it to the package The depscan tool is used to determine dependencies and map them to a component (e.g. libglib2 is part of the GLib2 component) Package is GPG-signed afterwards During installation, a few optimizations and adjustments are made automatically A Listaller IPK installation does not run any user-defined script Listaller packages are simple LZMA2 -compressed tarballs

  83. The Problem AppStream Listaller Conclusion Utopia package creation 1 Write AppStream AppData describing the application 2 Write a small pkoptions file, defining few basic options for the package 3 Write a file/dir listing for the new package 4 Build the package! Listaller will use appcompile to determine the buildsystem and build the app, install it to a temporary location and then add it to the package The depscan tool is used to determine dependencies and map them to a component (e.g. libglib2 is part of the GLib2 component) Package is GPG-signed afterwards During installation, a few optimizations and adjustments are made automatically A Listaller IPK installation does not run any user-defined script Listaller packages are simple LZMA2 -compressed tarballs

  84. The Problem AppStream Listaller Conclusion Utopia package creation 1 Write AppStream AppData describing the application 2 Write a small pkoptions file, defining few basic options for the package 3 Write a file/dir listing for the new package 4 Build the package! Listaller will use appcompile to determine the buildsystem and build the app, install it to a temporary location and then add it to the package The depscan tool is used to determine dependencies and map them to a component (e.g. libglib2 is part of the GLib2 component) Package is GPG-signed afterwards During installation, a few optimizations and adjustments are made automatically A Listaller IPK installation does not run any user-defined script Listaller packages are simple LZMA2 -compressed tarballs

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend

sysctlinfo: a new interface to visit the FreeBSD sysctl MIB and to pass the objects info to

sysctlinfo: a new interface to visit the FreeBSD sysctl MIB and to pass the objects info to

sysctlinfo: a new interface to visit the FreeBSD sysctl MIB and to pass the objects info to userland Alfonso Sabato Siciliano alfonso.siciliano@email.com BSDCan 2020, Ottawa, Canada Abstract known as sysctl MIB-Tree or sysctl tree . Listing 1:

332 views • 7 slides
SOEs Reform and Governance Andrew Sheng Chairman Securities and Futures Commission 23 June 2005

SOEs Reform and Governance Andrew Sheng Chairman Securities and Futures Commission 23 June 2005

SASAC Lecture SOEs Reform and Governance Andrew Sheng Chairman Securities and Futures Commission 23 June 2005 Contents of Lecture Objectives of State Ownership Governance. How to monitor SOE performance through better governance.

384 views • 25 slides
Reactive Systems Dave Farley http://www.davefarley.net @davefarley77 Reactive Systems 21st

Reactive Systems Dave Farley http://www.davefarley.net @davefarley77 Reactive Systems 21st

Reactive Systems Dave Farley http://www.davefarley.net @davefarley77 Reactive Systems 21st Century Architecture for 21st Century Problems Dave Farley http://www.davefarley.net @davefarley77 http://www.continuous-delivery.co.uk Our World Is

951 views • 38 slides
Evidence for a posteriori security Alexander Hicks, Steven J. Murdoch University College London

Evidence for a posteriori security Alexander Hicks, Steven J. Murdoch University College London

Evidence for a posteriori security Alexander Hicks, Steven J. Murdoch University College London Evidence? Liability Accountability Law Due process Auditability Verifiability Integrity Proof

448 views • 15 slides
Git it Together Beginner Slides Paul Johnson 1 1 Center for Research Methods and Data Analysis

Git it Together Beginner Slides Paul Johnson 1 1 Center for Research Methods and Data Analysis

Git it Together Beginner Slides Paul Johnson 1 1 Center for Research Methods and Data Analysis 2018 Paul Johnson (K.U.) Git it Together 2018 1 / 71 Outline Motivation 1 Git BASH: Gitting to Know You 2 3 Common Scenarios 3 Scenario 1:

1.05k views • 71 slides
CS3157: Advanced Programming Lecture #10 June 26 Shlomo Hershkop shlomo@cs.columbia.edu 1

CS3157: Advanced Programming Lecture #10 June 26 Shlomo Hershkop shlomo@cs.columbia.edu 1

CS3157: Advanced Programming Lecture #10 June 26 Shlomo Hershkop shlomo@cs.columbia.edu 1 Outline wrap up CPP templates file handling Reading: chapters 20 Advanced Topics Review for final 2 1

1.65k views • 128 slides
Vulnerabilities: Malicious Code Class 10 P&P: Ch 3.3, 3.4 1 CIS-5372: 9.Nov.2011

Vulnerabilities: Malicious Code Class 10 P&P: Ch 3.3, 3.4 1 CIS-5372: 9.Nov.2011

Vulnerabilities: Malicious Code Class 10 P&P: Ch 3.3, 3.4 1 CIS-5372: 9.Nov.2011 Announcement Presence sheet Solution to Homework 2 is out Grades will follow 2 CIS-5372: 9.Nov.2011 What Did We Cover Before ?

1.02k views • 71 slides
Outline Operating System Security Introduction CS 239 Memory protection

Outline Operating System Security Introduction CS 239 Memory protection

Outline Operating System Security Introduction CS 239 Memory protection Interprocess communications protection Security for Networks and File protection System Software Authentication May 20, 2002 Lecture 13 Lecture

348 views • 12 slides
Validation and Experimentation Board of Innovation The Growth Revolution Intro Validation

Validation and Experimentation Board of Innovation The Growth Revolution Intro Validation

Validation and Experimentation Board of Innovation The Growth Revolution Intro Validation of new Ventures Experimentation Process Assumptions Hypotheses Experiment Types Metrics Wrap-up Introductions HI THERE! 3 ABOUT US

1.08k views • 86 slides
BoardGame: A MiniDraw extension Henrik Brbak Christensen Status: Draft. November 29, 2010

BoardGame: A MiniDraw extension Henrik Brbak Christensen Status: Draft. November 29, 2010

BoardGame: A MiniDraw extension Henrik Brbak Christensen Status: Draft. November 29, 2010 Chapter 1 Boardgame Architecture The MiniDraw framework is described in Chapter 30 in Flexible, Reliable Software . The Boardgame extension is a set of

481 views • 20 slides
Routing Security Training Course Training Services | RIPE NCC | November 2015 Schedule 09:00 -

Routing Security Training Course Training Services | RIPE NCC | November 2015 Schedule 09:00 -

Routing Security Training Course Training Services | RIPE NCC | November 2015 Schedule 09:00 - 09:30 Co ff ee, Tea 11:00 - 11:15 Break 13:00 - 14:00 Lunch 15:30 - 15:45 Break 17:30 End Routing Security 2 Introductions Name

1.66k views • 139 slides
Final Exam Review CS 349 - Spring 2017 Wednesday, August 09 th , 4:00 to 6:30 PM (2.5 hours)

Final Exam Review CS 349 - Spring 2017 Wednesday, August 09 th , 4:00 to 6:30 PM (2.5 hours)

Final Exam Review CS 349 - Spring 2017 Wednesday, August 09 th , 4:00 to 6:30 PM (2.5 hours) What to Expect PAC 4,5 assigned seats (Odyssey) Entrance to PAC from the Ring Road side through the Red South or Blue South doors (Red

498 views • 32 slides
Federation monitoring Jaime Prez < jaime.perez@ j p @ rediris.es> Virginia

Federation monitoring Jaime Prez < jaime.perez@ j p @ rediris.es> Virginia

TF-NOC meeting Brussels, October 2011 Federation monitoring Jaime Prez < jaime.perez@ j p @ rediris.es> Virginia Martn-Rubio < virgini ia.martinrubio@rediris.es> What is an identity fed deration? A set of

585 views • 29 slides
Contents 1 Backgrounds 2 Related Work 3 IOVTee 4 Evaluation 5 Conclusion 2

Contents 1 Backgrounds 2 Related Work 3 IOVTee 4 Evaluation 5 Conclusion 2

Best Paper Award IOVTee : A Fast and Pragmatic Software-based Zero-copy/Pass-through Mechanism for NFV-nodes Assist. Prof. Ryota Kawashima Nagoya Institute of Technology, Japan 1 Contents 1 Backgrounds 2 Related Work 3 IOVTee 4

483 views • 24 slides
How to Store and Use Bitcoins Simple Local Storage Hot and Cold Storage Splitting and

How to Store and Use Bitcoins Simple Local Storage Hot and Cold Storage Splitting and

Cryptocurrency Technologies How to Store and Use Bitcoins How to Store and Use Bitcoins Simple Local Storage Hot and Cold Storage Splitting and Sharing Keys Online Wallets and Exchanges Payment Services Transaction Fees

397 views • 28 slides
Human-Computer Interaction 15. Evaluating User Interface Recap: What is critique? Show a project

Human-Computer Interaction 15. Evaluating User Interface Recap: What is critique? Show a project

Human-Computer Interaction 15. Evaluating User Interface Recap: What is critique? Show a project in progress through prototypes Get solicit feedback from peers (small groups work best) Design critiques help you broaden your communication

509 views • 36 slides
gLite on Grid5000 : towards a real-size testbed for production grids S ebastien Badia and

gLite on Grid5000 : towards a real-size testbed for production grids S ebastien Badia and

gLite on Grid5000 : towards a real-size testbed for production grids S ebastien Badia and Lucas Nussbaum Partially funded by Simglite project Appel Interfaces Recherche en grilles Grilles de production Institut des Grilles du CNRS

575 views • 8 slides
Outline Usability and security (contd) Elections and their security CSci 5271 Introduction

Outline Usability and security (contd) Elections and their security CSci 5271 Introduction

Outline Usability and security (contd) Elections and their security CSci 5271 Introduction to Computer Security Announcements intermission Day 24: Electronic voting System security of electronic voting Stephen McCamant Exercise sets 2

424 views • 10 slides
Aaron Chaisson UIs are one of the single most important design aspects to games, bad UI can

Aaron Chaisson UIs are one of the single most important design aspects to games, bad UI can

Aaron Chaisson UIs are one of the single most important design aspects to games, bad UI can ruin a great game. Also the interface is the most discussed component in game reviews. However, you are greatly restricted due to the most important

741 views • 32 slides
Today 1 | www.ebsco.com Topics to Cover What are Intermediaries? Todays challenges The new

Today 1 | www.ebsco.com Topics to Cover What are Intermediaries? Todays challenges The new

UKSG Introduction to E-Resources Today 1 | www.ebsco.com Topics to Cover What are Intermediaries? Todays challenges The new consultative approach Technologies 2 | www.ebsco.com Family-owned, & Dedicated to Libraries, serving

855 views • 52 slides
1 User-Centered Design (Gould) Focus on users and their tasks early and often in the design

1 User-Centered Design (Gould) Focus on users and their tasks early and often in the design

ICS 463 Human Computer Interaction 9. User-Participation and Prototyping Dan Suthers Spring 2004 User-Centered Approaches (Consider this an extension of the previous two chapters on requirements analysis and design) Why involve users?

439 views • 13 slides
and Privacy in Online Social Networks Ralph Gross Alessandro Acquisti Presenter: Chris Kelley

and Privacy in Online Social Networks Ralph Gross Alessandro Acquisti Presenter: Chris Kelley

Information Revelation and Privacy in Online Social Networks Ralph Gross Alessandro Acquisti Presenter: Chris Kelley Outline Motivation Online Vs. Offline Networks Online Social Networks - Privacy Implications Analysis: The

635 views • 41 slides
Any Data, Anytime, Anywhere Dan Bradley <dan@hep.wisc.edu> representing the AAA Team At

Any Data, Anytime, Anywhere Dan Bradley <dan@hep.wisc.edu> representing the AAA Team At

Any Data, Anytime, Anywhere Dan Bradley <dan@hep.wisc.edu> representing the AAA Team At OSG All Hands Meeting March 2013, Indianapolis AAA Project Goal Use resources more effectively through remote data access in CMS Sub-goals

436 views • 24 slides
CMS remote data access (AAA) Giacinto DONVITO (INFN-Bari)

CMS remote data access (AAA) Giacinto DONVITO (INFN-Bari)

CMS remote data access (AAA) Giacinto DONVITO (INFN-Bari) Thanks to: Brian Bockelman, Ken Bloom (UNL) Tommaso Boccali, Daniele Bonacorsi (INFN) AAA

359 views • 24 slides

More recommend