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

[Feature request]: Uninstall flatpak package from specific remote #5545

Open
2 tasks done
p5 opened this issue Oct 2, 2023 · 1 comment
Open
2 tasks done

[Feature request]: Uninstall flatpak package from specific remote #5545

p5 opened this issue Oct 2, 2023 · 1 comment

Comments

@p5
Copy link

p5 commented Oct 2, 2023

Checklist

  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Suggestion

It would be good if we can specify which remote we wish to remove the Flatpak package from.
I have ran into situations where the same package is installed from Fedora's remote and Flathub's remote. I want to be able to specify in-line (so it can be scripted) that the Fedora one should be removed, not touching the Flathub one.

The command would be something like this:

$ flatpak uninstall --remote fedora $package
@p5 p5 added the enhancement label Oct 2, 2023
@chrisawi
Copy link
Collaborator

This can only happen if the fedora and flathub remotes are added to different installations (i.e. system vs user). An app can only be installed once in a specific installation. Thus, you can use --system or --user to disambiguate.

For scripting, you could employ flatpak info --show-origin.

If implemented, this option should probably be called --origin to match existing usage. It might also be useful in combination with --all, although you can achieve a similar result with remote-delete if you're planning to delete the remote afterward anyway.

I can't imagine this specific scenario is very common because both remotes are added to the system installation by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants