This is a multi-part message in MIME format.
--nextPart1879525.tmr0rYB4Vy
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
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[1]
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.
On Wednesday, February 14, 2024 9:31:14 AM MST
c.buhtz@posteo.jp wrote:
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
soren@debian.org
--------
[1]
https://salsa.debian.org/cryptocoin-team/electrum/-/blob/master/debian/ electrum.install?ref_type=heads
--nextPart1879525.tmr0rYB4Vy
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="UTF-8"
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">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.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><a href="
https://salsa.debian.org/cryptocoin-team/electrum/-/blob/master/debian/electrum.install?ref_type=heads">https://salsa.debian.org/cryptocoin-team/electrum/-/blob/master/
debian/electrum.install?ref_type=heads</a></p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">In this case I wrote the AppStream file