Commit graph

12 commits

Author SHA1 Message Date
Yaakov Selkowitz
86101a593f F44 2026-03-24 20:37:01 -04:00
Yaakov Selkowitz
26f5164857 F43 2025-10-12 13:01:14 -04:00
Yaakov Selkowitz
c7f7d06072 F42 2025-03-30 18:46:07 -04:00
Yaakov Selkowitz
345a4ec8d4 Add tools 2025-01-07 21:39:02 -05:00
Yaakov Selkowitz
0b7f98a24d F41 2024-10-08 12:48:11 -04:00
Yaakov Selkowitz
40574e82df F40 2024-04-11 02:13:21 -04:00
Kalev Lember
cc5d7ae372 Switch to F39 2023-10-19 12:00:47 +02:00
Kalev Lember
cb5cc514b3 Adapt for renamed app ID
Upstream has renamed the app ID from darktable.desktop to
org.darktable.darktable, which is sadly different from
org.darktable.Darktable that the flatpak is using.

For now, keep on using org.darktable.Darktable. When we update the
runtime to F38, that would be a good point to rename the flatpak app ID
if we want to go ahead with the rename to match the new upstream naming.

Looks like flathub is also sticking with org.darktable.Darktable for
now.

https://github.com/darktable-org/darktable/pull/13193
https://github.com/flathub/org.darktable.Darktable/pull/101
2023-02-24 16:28:28 +01:00
Kalev Lember
d4d35895d8 container.yaml: Sync finish-args with flathub 2022-09-14 19:32:54 +02:00
Kalev Lember
282cf21e9f container.yaml: Adapt for master->stable rename 2021-02-08 12:41:59 +01:00
Kalev Lember
d6fcbd4a2d Sync finish-args from flathub 2020-03-12 16:39:33 +01:00
Kalev Lember
48fb913a01 Initial import 2019-07-17 20:37:35 +03:00