Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

How to provide AppStream data by upstream?

3 views
Skip to first unread message

c.b...@posteo.jp

unread,
Feb 14, 2024, 11:40:07 AM2/14/24
to
Hello,

imagine an upstream project providing an AppStream data file
(foobar.metainfo.xml) and it is a full qualified Python project using
state of the art build system (pyproject.toml, setuptools or something
similiar, src-layout).

Should the foobar.metainfo.xml file be a part of the upstream build
process (e.g. as custom build step in setuptools)? Or shouldn't that
file be involved in the upstreams Python-native build process?
Does distro maintainers (you) recognize the existance of such files and
you take care yourself via an exceptional magic debian-build-rule that
this file is part of the deb-package and installed into
/usr/share/metainfo/ ?

What is your preferet way?

The location /usr/share/metainfo is specified by freedesktop.org and
should be the same on all distros. But their might be exceptions.

The question is who is responsible for locating that xml file into the
correct place? How can decide what the correct place is?

Thanks
Christian

Soren Stoutner

unread,
Feb 14, 2024, 5:20:04 PM2/14/24
to

I don’t know if this would be considered the best way to do it, but with electrum I simply handle the AppStream file manually in electrum.install.


https://salsa.debian.org/cryptocoin-team/electrum/-/blob/master/debian/electrum.install?ref_type=heads


In this case I wrote the AppStream file myself and submitted it to the upstream project, which is now maintaining it in their code base.

--

Soren Stoutner

so...@debian.org

signature.asc
0 new messages