3 ms·

Flatpak itself is not enforcing this. You can ship a statically linked binary with no dependencies if you want. The runtime thing that flatpak supports is, iro

Flatpak itself is not enforcing this. You can ship a statically linked binary with no dependencies if you want. The runtime thing that flatpak supports is, ironically, to minimize and deduplicate common dependencies, and to be fair they are only downloaded with the first app that needs it with many apps using the same handful of runtimes. The fetish for shared dependencies within Linux and the pains it causes are a bit frustrating, but that's not new to flatpak. > What's even more insane is at the command line when you Tab to autocomplete the thing makes network requests and hangs! It's the only CLI app I know what requires the internet to autocomplete! nit: CLI tools do not implement auto-complete themselves. What you are seeing are auto-complete scripts for your shell that make network connections. Not sure if flatpak keeps a local repo list. That would be the only way to implement tab-completion of installable items without making network connections.

contrarian1234 3y ago
It does not keep a repo list bc the CLI needs to be constantly directed to the particular repo you want to use/inspect. It doesn't default to flathub and there is no sources.list equivalent. So therefore there is no cache and it needs to constantly ping the server to do anything. This makes the whole interface incredibly sluggish to the point that it's frustrating to navigate and explore. So you end up using the crappy website (as compared to something snappy like aptitude) Frankly shared dependencies makes sense when they're sort of wide-consensus. Debian-stable or Ubuntu-LTS. Everyone is building to work with the same set of version numbers and they are all rock stable for years. Rolling shared dependencies is just a recipe for broken apps. It's just a combinatorics problem. You can't test against every combination of every version of all your dependencies. And multiversion shared dependencies .. I don't even understand the point (and why Nix has always confused me)
- tapoxi 3y ago
  There is shared consensus: https://docs.flatpak.org/en/latest/available-runtimes.html https://docs.flatpak.org/en/latest/available-runtimes.html
IshKebab 3y ago
> CLI tools do not implement auto-complete themselves. What you are seeing are auto-complete scripts for your shell that make network connections. nit: This is incorrect. Robust auto-complete scripts call the actual program to provide completions. That is what Flatpak does. It is Flatpak itself that makes the network connections. https://github.com/flatpak/flatpak/blob/main/completion/flatpak#L9 https://github.com/flatpak/flatpak/blob/main/completion/flat... Not that it would make any differencen if it was implemented in Bash seeing as the Bash script is also provided by Flatpak.
- deleted 3y ago
  [deleted]

contrarian1234 3y ago

It does not keep a repo list bc the CLI needs to be constantly directed to the particular repo you want to use/inspect. It doesn't default to flathub and there is no sources.list equivalent. So therefore there is no cache and it needs to constantly ping the server to do anything. This makes the whole interface incredibly sluggish to the point that it's frustrating to navigate and explore. So you end up using the crappy website (as compared to something snappy like aptitude) Frankly shared dependencies makes sense when they're sort of wide-consensus. Debian-stable or Ubuntu-LTS. Everyone is building to work with the same set of version numbers and they are all rock stable for years. Rolling shared dependencies is just a recipe for broken apps. It's just a combinatorics problem. You can't test against every combination of every version of all your dependencies. And multiversion shared dependencies .. I don't even understand the point (and why Nix has always confused me)

tapoxi 3y ago
There is shared consensus: https://docs.flatpak.org/en/latest/available-runtimes.html https://docs.flatpak.org/en/latest/available-runtimes.html

IshKebab 3y ago

> CLI tools do not implement auto-complete themselves. What you are seeing are auto-complete scripts for your shell that make network connections. nit: This is incorrect. Robust auto-complete scripts call the actual program to provide completions. That is what Flatpak does. It is Flatpak itself that makes the network connections. https://github.com/flatpak/flatpak/blob/main/completion/flatpak#L9 https://github.com/flatpak/flatpak/blob/main/completion/flat... Not that it would make any differencen if it was implemented in Bash seeing as the Bash script is also provided by Flatpak.

deleted 3y ago
[deleted]