Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #15476 > unrolled thread
| Started by | c.buhtz@posteo.jp |
|---|---|
| First post | 2024-02-14 17:40 +0100 |
| Last post | 2024-02-14 23:20 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.maint.python
How to provide AppStream data by upstream? c.buhtz@posteo.jp - 2024-02-14 17:40 +0100
Re: How to provide AppStream data by upstream? Soren Stoutner <soren@debian.org> - 2024-02-14 23:20 +0100
| From | c.buhtz@posteo.jp |
|---|---|
| Date | 2024-02-14 17:40 +0100 |
| Subject | How to provide AppStream data by upstream? |
| Message-ID | <I7qsI-a8fn-17@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Soren Stoutner <soren@debian.org> |
|---|---|
| Date | 2024-02-14 23:20 +0100 |
| Message-ID | <I7vLH-abx3-3@gated-at.bofh.it> |
| In reply to | #15476 |
[Multipart message — attachments visible in raw view] — view raw
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web