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

refactor: Convert flatpak-manager into a module #45

Merged
merged 20 commits into from
Oct 1, 2023

Conversation

zelikos
Copy link
Owner

@zelikos zelikos commented Oct 1, 2023

Closes #44

Prototyping this here before opening PRs upstream. Will need to do one in both startingpoint and bling

We're only enabling the Flatpak-related services, and those are being
converted into a separate module.
@zelikos zelikos marked this pull request as draft October 1, 2023 15:48
@zelikos zelikos force-pushed the flatpak-manager-module branch from 3d08c9f to 8ddfb3a Compare October 1, 2023 17:50
Had them there for testing, don't need them to stay.
System-wide was flathub-system, per-user was flathub-user. I do like
having it explicit like that myself, but for more general-purpose usage,
it's probably best to keep it generic as just flathub for both. Flatpak
does allow specifying --system or --user already, anyway.
Since I'm switching back to using "flathub" as the remote name instead
of specifying -user vs -system
@zelikos zelikos marked this pull request as ready for review October 1, 2023 19:36
@zelikos zelikos enabled auto-merge (squash) October 1, 2023 19:36
@zelikos zelikos merged commit 7f7c42b into live Oct 1, 2023
@zelikos zelikos deleted the flatpak-manager-module branch October 1, 2023 22:32
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.

Convert zeliblue-flatpak-manager into module
1 participant