Upstream software project

brp-extract-appdata

Extract appdata.xml

About brp-extract-appdata

Extract appdata.xml

This project links 2 native package records across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

brp-extract-appdata repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Leap 15.6: 2 package records. Catalog coverage diagram, not an application screenshot.brp-extract-appdata: recorded package coverageopenSUSE Leap 15.62 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
brp-extract-appdata
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-leap-15-6
License expression
MIT
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

OBS generated appdata.xml contains all icons and this little tool splits the XML into the format expected from software center

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Leap 15.6

  1. Package brp-extract-appdata

    leap-15.6 (openSUSE Leap 15.6) (Development/Tools/Building): Extract appdata.xml

    2016.05.04-1.23: noarch

    Source: brp-extract-appdata

  2. Package extract-appdata-icons

    leap-15.6 (openSUSE Leap 15.6) (Development/Tools/Building): A little perl script to split appdata.xml

    2016.05.04-1.23: noarch

    Source: brp-extract-appdata

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.