postmarketOS specific appstream-data
I haven't looked into it in detail, but given that we have our own packages, it would probably make sense to have a postmarketOS specific appstream-data package as well. Discussion input and ideas welcome.
Activity
added category::infrastructure discussion labels
mentioned in issue #698 (closed)
By Oliver Smith on 2020-07-28T18:00:22
We use the following docker container: https://gitlab.alpinelinux.org/alpine/infra/docker/appstream-generator
And the following docker-compose: https://gitlab.alpinelinux.org/alpine/infra/compose/appstream-generator
Adjusting asgen-config.json in the compose repo should be sufficient
By Rasmus Thomsen on 2020-07-28T19:28:59
mentioned in merge request !1512 (closed)
By Luca Weiss on 2020-08-30T16:12:59
mentioned in merge request !1597 (closed)
By Oliver Smith on 2020-09-22T07:36:17
-
@Cogitri made it nicer in alpine, now the separate package is not needed.
!1597 (closed) adjusts our fork too (for master, the alpine appstream data package is still available on 3.12).
So the next step for postmarketOS specific appdata is setting up the appstream-generator on our infrastructure. @MartijnBraam or I could do it (but we also have other tasks). Let's try to get this done within the next two weeks.
We also need to adjust the packages on v20.05 and make sure that the update works properly. This could either be done now (help wanted) or when we have the pmOS specific appdata.
By Oliver Smith on 2020-09-22T07:44:09
-
now the separate package is not needed.
might still be needed for discover
By Alexey Min on 2020-09-23T09:34:20
Edited by Ghost User -
For reference, this is being discussed here: #506 (comment 416514735)
By Oliver Smith on 2020-09-23T09:34:20
-
I had apstream-generator run on the master branch now, it's output is online at: http://mirror.postmarketos.org/appstream/
It seems appstream-generator has some issues with us not using sections though.
By Martijn Braam on 2020-11-02T16:12:47
mentioned in merge request !1679 (closed)
By Oliver Smith on 2020-11-04T09:39:12
-
So what should URLs to tarballs be like? For example http://mirror.postmarketos.org/appstream/master/Components-community-aarch64.xml.gz 404s
By Alexey Min on 2020-11-04T13:02:29
Edited by Ghost User -
Hmm I have similar files but they're outside the html dir from the generated appstream data...
pmos-web:/var/cache/appstream/export/data/master$ ls CID-Index--aarch64.json.gz CID-Index--x86_64.json.gz Components--armhf.xml.xz Components--x86.xml.xz CID-Index--armhf.json.gz Components--aarch64.xml.gz Components--armv7.xml.gz Components--x86_64.xml.gz CID-Index--armv7.json.gz Components--aarch64.xml.xz Components--armv7.xml.xz Components--x86_64.xml.xz CID-Index--x86.json.gz Components--armhf.xml.gz Components--x86.xml.gz icons--aarch64-64x64.tar.gzThe html is in /var/cache/appstream/export/html/master, i'm not really sure what the directory structure of appstream data should be
By Martijn Braam on 2020-11-04T13:02:29
-
So Alpine has (for aarch64):
- https://appstream.alpinelinux.org/data/edge/main/Components-main-aarch64.xml.gz
- https://appstream.alpinelinux.org/data/edge/community/Components-community-aarch64.xml.gz
Maybe doesn't matter much which structure, but it should be possible to download them?
(maybe we should also have main/community/testing..)
By Alexey Min on 2020-11-04T13:13:58
-
https://mirror.postmarketos.org/appstream/data/master/
By Martijn Braam on 2020-11-04T13:16:24
mentioned in issue #1384 (closed)
By Pablo Correa Gomez on 2022-01-11T23:06:05
-
I've noticed GNOME software is missing appstream data, and https://mirror.postmarketos.org/appstream/data/ doesn't seem up to date. I think the data just isn't regenerated at the moment.
By Antoine Fontaine on 2022-12-12T17:12:40
Edited by Ghost User -
To be fair, that probably is not necessary at all in the long-term. Unless pmOS is expecting to ship some graphical application which will not ever make it to alpine or the corresponding upstream, having pmOS specific appstream-data does not make much sense. It maybe did 2 years ago at a point where there were many forked apps in
temp. But I do not think that is the case anymore, and even pmOS tweaks is slowly on its way to the retirement home :)By Pablo Correa Gomez on 2022-12-13T02:40:27
Edited by Ghost User -
I guess then someone would have to contribute this to Alpine
...
Le 12 décembre 2022 18:12:41 GMT+01:00, "Pablo Correa Gomez (@pabloyoyoista)" gitlab@mg.gitlab.com a écrit :
Pablo Correa Gomez commented on a discussion: #699 (comment 1205988025)
To be fair, that probably is not necessary at all in the long-term. Unless pmOS is expecting to ship some graphical application which will not ever make it to alpine or the corresponding upstream, having pmOS specific appstream-data does not make much sense. It maybe did 2 years ago at a point where there were many forked apps in
temp. But I do not think that is the case anymore, and even pmOS tweaks is slowly on its way to the retirement home :)-- Reply to this email directly or view it on GitLab: #699 (comment 1205988025) You're receiving this email because of your account on gitlab.com.
By Antoine Fontaine on 2022-12-14T17:27:57
-
That's been working for a while ;) https://appstream.alpinelinux.org/
By Pablo Correa Gomez on 2022-12-14T17:29:10
-
This item should simply be closed. This is no longer necessary :)
By Pablo Correa Gomez on 2023-02-08T18:08:06
Edited by Ghost User