Fedora 22 To Push For Requiring Packages To Have AppData

[PiotrDrag]

I'm also not sure why they don't use RPM fields for that

That's because a package is not an application. It may contain one. Or three. Or none.

[Thaodan]

And I can also understand GNOME, given that they wanted a cross-package spec as opposed to one bound to either RPM or DEB.

This is what packagekit is for.

[RahulSundaram]

This is what packagekit is for.

PackageKit is an API. You need underlying metadata for the API to access. In this case, that metadata is Appdata

[zxy_thf]

That's because a package is not an application. It may contain one. Or three. Or none.

In most cases, it contains a piece.

[Delgarde]

I'm also not sure why they don't use RPM fields for that, but I guess that it's faster when the file is outside the package, or something? And I can also understand GNOME, given that they wanted a cross-package spec as opposed to one bound to either RPM or DEB.

How would the data for those RPM fields come from? Hint... AppData might be the answer...

[GreatEmerald]

How would the data for those RPM fields come from? Hint... AppData might be the answer...

The answer is a SPEC file.

[plonoma]

The Linux world really needs some more standardization for user software.
AppData and AppStream are very useful things in that direction.

[Delgarde]

The answer is a SPEC file.

A SPEC file is RPM-specific configuration, usually provided by the distro packager rather than upstream. The AppData file is intended to be part of the upstream source package... something useful whether you're packaging for RPM, DEB, or one of those zero-install type packages.