Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(default-flatpaks): Obtain flatpak list of apps without runtimes #142

Merged
merged 1 commit into from
Feb 25, 2024

Conversation

fiftydinar
Copy link
Collaborator

Since runtimes are not supported in our module, we don't need them in a flatpak list inside binaries.

Since runtimes are not supported in our module, we don't need them in a flatpak list inside binaries.
@xynydev
Copy link
Member

xynydev commented Feb 24, 2024

I still don't know why runtimes aren't supported...

@fiftydinar
Copy link
Collaborator Author

I still don't know why runtimes aren't supported...

  1. I mentioned this once, but it's because Universal Blue images & ublue-update automatically remove unused flatpak dependencies, which can possibly remove runtime that user specified in the module recipe itself.

  2. Another reason is that most flatpak runtimes have unstable branch versioning, which change over time.
    Users would need to change flatpak runtime versioning every time it updates, which is not very convenient at all.

  3. Related to 2. reason, detection of same flatpak runtimes with different versions is tricky to do, which would be needed to detect which flatpak runtimes should remain as user specified runtime & which should not.
    However, even If I implemented this, it could still happen that runtime gets automatically removed by using flatpak uninstall --unused, which is outlined in 1. reason.

@xynydev xynydev merged commit fec6a76 into blue-build:main Feb 25, 2024
2 checks passed
@fiftydinar fiftydinar deleted the flatpaks-tweak branch February 25, 2024 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants