https://bugs.kde.org/show_bug.cgi?id=501276
--- Comment #2 from Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> --- (In reply to John Kizer from comment #1) > could you help articulate your use case for using Discover (a GUI tool) from > the command-line in this situation, rather than the CLI package managers that > you listed? Automation scripts for myself. It's a lot easier, in *some* situations, to utilise Discover in the stead of 12 different command-line package management interfaces, when I'm going to run a script across multiple OSes. That's why I utilised a flatpak reference file in the examples. I expect you're now thinking, "just use `flatpak` then", but that would be using another PM CLI, whereas Discover already supports every backend possible. Considering that PackageKit doesn't appear to support `.flatpak` files, I'd have to stay this highly abstracted to not at least delegate to `pkcon` and `flatpak`. It's definitely niche, since just downloading a file beforehand isn't a terrible amount of work. Though, a better error message would be useful regardless, if it's undesirable, considering that all the lower-level alternatives aforereferenced support HTTP URIs (albeit, ironically, not file URIs, unlike Discover). -- You are receiving this mail because: You are watching all bug changes.
