Re: Packaging guidelines - validation of AppStream metadata files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Sep 24, 2023 at 2:46 AM Mattia Verga via devel
<devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Il 24/09/23 01:18, Neal Gompa ha scritto:
> > On Sat, Sep 23, 2023 at 6:05 PM Michael Catanzaro <mcatanzaro@xxxxxxxxxx> wrote:
> >> On Sat, Sep 23 2023 at 10:26:48 PM +0200, Alexander Ploumistos
> >> <alex.ploumistos@xxxxxxxxx> wrote:
> >>> Could someone involved
> >>> with AppStream please provide some information? Shouldn't our
> >>> documentation be changed to reflect these changes? Does the FPC need
> >>> to decide on this?
> >>   From upstream perspective: appstream-util is indeed obsolete. Upstream
> >> software should stop using it and switch to appstreamcli instead.
> >>
> >> But as you've noticed, it seems Fedora isn't ready for that yet....
> > Ultimately, appstream-util's output is what matters since we use
> > appstream-builder (from appstream-glib) to generate our AppStream
> > metadata index. If it doesn't pass that tool, it doesn't show up.
> >
> If upstream switched to appstreamcli, what tool do they use to generate
> the index to not fail validation?
> Can Fedora switch to that other tool?
>

There was no switching. Both appstream-util and appstreamcli are
considered conformant.

Ultimately, the only way we can stop relying on appstream-glib is if
appstream-builder[1] was reimplemented on top of libappstream-compose.

Long ago, I tried to see if we could have our AppStream data produced
as repodata instead of a package, but the answer I got was that we
need the functionality added to createrepo to do it[2]. If someone
ever got around to making that happen, a lot of things in our pipeline
could be simplified.

[1]: https://github.com/hughsie/appstream-glib/tree/main/libappstream-builder
[2]: https://github.com/rpm-software-management/createrepo_c/issues/75

-- 
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux