On Mon, 2020-03-09 at 09:50 +0100, Vitaly Zaitsev via rpmfusion-
developers wrote:
On 07.03.2020 20:00, Sérgio Basto wrote:
> Sorry , I don't understand what you mean , can you explain with
more
> detail your plan ?
Fedora should stay with upstream, so I suggest the following:
1. add missing appdata manifests directly into RPM packages. We can
use
this tool[1];
2. open pull requests to upstream with created/generated appstream
data
files (should be also integrated into their build system, but in the
most cases this is a trivial operation);
3. after updating all non-library RPM packages we can use
appstream-builder[2] to extract metadata into a separate
rpmfusion-appstream-data package.
I can help with this. We should start from creating the list of
non-library RPM Fusion packages with missing appdata manifests.
OK for me , the list of missing appdata can be based on [5] , I think
that was the list of missing appdata ...
On point 3, quoting "rpmfusion is already using that, it's how the
rpmfusion-{free,nonfree}-appstream-data packages[3] are constructed[4]"
[3]:
https://pkgs.rpmfusion.org/cgit/free/rpmfusion-free-appstream-data.git/tr...
[4]:
https://pkgs.rpmfusion.org/cgit/free/rpmfusion-free-appstream-data.git/tr...
[5]
https://github.com/sanjayankur31/rpmfusion-appdata/tree/master/appdata-ex...
https://github.com/sanjayankur31/rpmfusion-appdata/tree/master/appdata-ex...
--
Sérgio M. B.