Rebase on freedesktop platform#220
Conversation
Because a project that uses elementary Flatpak Platform with
blueprint-compiler fails to build without it, which was probably
included in GNOME Flatpak Platform:
Found ninja-1.13.2 at /usr/bin/ninja
[1/50] Generating data/blueprints with a custom command
FAILED: [code=1] data
/app/bin/blueprint-compiler batch-compile data/. ../data ../data/ui/help-overlay.blp
Traceback (most recent call last):
File "/app/bin/blueprint-compiler", line 40, in <module>
from blueprintcompiler import main
File "/app/lib/python3.13/site-packages/blueprintcompiler/main.py", line 27, in <module>
from . import formatter, interactive_port, linter, parser, tokenizer
File "/app/lib/python3.13/site-packages/blueprintcompiler/interactive_port.py", line 25, in <module>
from . import decompiler, parser, tokenizer
File "/app/lib/python3.13/site-packages/blueprintcompiler/decompiler.py", line 26, in <module>
from .gir import *
File "/app/lib/python3.13/site-packages/blueprintcompiler/gir.py", line 25, in <module>
import gi # type: ignore
^^^^^^^^^
ModuleNotFoundError: No module named 'gi'
[2/50] Merging translations for data/com.github.ryonakano.reco.Devel.metainfo.xml
ninja: build stopped: subcommand failed.
|
OK, it seems working as expected. An app built on Daily runtime of latest 2026-03-14.20.50.04.movand this branch: 2026-03-14.20.53.32.mov |
|
@danirabbit Hi, I'd like to hear your opinion here. This PR does fix the big cursor issue on OS 8 at least with Reco as seen in the above screencasts. However, I have the following concern. Which route do you think we should go? My concern: Some apps might require newer GTK versions that reproduces the issueAs far as I tested it's GTK 4.18.6 that is the last version that does not reproduce the big cursor issue on OS 8. And it's libadwaita 1.7.x that is the last version that can build with GTK 4.18.6. However, some of GNOME apps that we package requires newer versions:
So, I have a concern that we need to stack on older version of these apps until we drop support for OS 8 completely, which could be a long time. Alternatively we can build and install newer GTK and libadwaita that these apps require in each manifest file, but that means the big cursor issue still occurs with these apps on OS 8 even if these manifests are based on this PR, which makes me feel this PR a bit useless. Possible routes
Footnotes |
|
@ryonakano Maybe we can hold onto the older GTK just until we release OS 9, so that way we can at least give people a way to update and avoid the bug? On the other hand, all the GNOME apps from Flathub now have this bug and there's nothing we can do to fix it, so maybe we just have to accept it for now? :/ I'm not sure there's a clear winning answer here. I do think there can be a point to basing on the free desktop platform because like you said we don't have to be tied to the short support window of the GNOME platform and currently I don't think we're doing a good job keeping up with minor releases so we probably can do platform releases more often if the dependency checker bot is alerting about new versions |
|
@danirabbit Thank you for your reply. I agree with your comment quoted below.
The issue is just the cursor looks bigger and nothing else like crash, so I think we can accept it as a known issue for now and wait for being resolved in OS 9.
Yes, I agree that we may want to rebase on fd.o platform for longer support term, but probably in flatpak-platform 9? I think we may want to keep basing on GNOME platform for now, in flatpak-platform 8.3, so that things won't break too much for developers when bumping from 8.2. |
Fixes #219
How to Test