8/2/2023 0 Comments Skhd portal![]() Even bubblewrap has all that's needed and it is included anyway because of Flatpak. For instance: why is podman required? The container functionality required is built into the kernel and podman has a lot of features that are entirely unused. ![]() I have my issues with both, but the base concept is sound. In my opinion, Flatpak should support a user-definable default permissions template that says "always permit", "always deny", and "don't care" for any given permission.Īctually I agree that when it comes to these collections of software to build an "environment" something like toolbox/distrobox is a better fit. As it is, Flatpaks can give themselves permission to $HOME without ever notifying me, which I think is just as silly. I want the ability to give a Flatpak those permissions, not that they be able to give them to themselves. See, here's the problem with letting packages determine their own defaults. > If Linux starts attracting commercial development and we see an influx of new apps, wouldn't you feel safe knowing that the ones you install as flatpaks aren't allowed to capture packets on your system? clangd with the LSP plugin in Sublime Text, execute CMake, use the embedded terminal (Terminus), or the debugger plugin with lldb. desktop files for the GUI ones so that I can launch them from the KDE app menu as if they were regular apps. I have all of my development tools installed in a single toolbox, and have. They’re podman containers with extra features to integrate with the host. A flatpak is the same, except that’s hard to get right for every development setup, so a toolbox just lets you do whatever you want with it. An IDE on Android usually needs to include all of the tools it needs. ).įlatpaks are kind of like Android APKs, except unlike Android, there’s actually an operating system worth interacting with. That’s why Silverblue ships with Toolbox (. Using development tools as a flatpak is usually not a good idea for many reasons. I haven’t had a reason to use IntelliJ, but I’m sure it would work the same way. I use Sublime Text, but I’ve also used VSCode, as well as a lot of other similar editors. The more things are packaged for Flatpak, the lower the burden for practical usage of distros maintained by small or new communities. This is good news for desktop Linux users in general, and especially good news for those of us who don't run Ubuntu or derivatives. I think it's clearly a good thing that the biggest and most popular desktop environments are coalescing around it. It's a much better way to manage third-party software than anything else we've got. And I trust it way more than an apt or dnf or pacman repo hosted by the likes of Zoom, Google, Discord, etc. Considering what it aims to do, it feels pretty fast, reliable, and neat. ![]() It seems to me that the engineers working on it have done a pretty good job of mitigating the downsides and risks, like library duplication and difficulty of shared updates, disk usage, etc. I think Flatpak does what it tries to do pretty well. I care about things like the extra storage overhead, the increased app startup time, the additional complexity associated with portals and sandboxing, the extent to which Flatpak applications do or don't support the available sandboxing features, and the orientation of Flatpak towards enabling a larger proprietary software ecosystem I'm not very interested in.īut despite all of that, and despite my interest in- and to some extent, commitment to- competing paradigms. I know many good reasons to prefer other means of installing packages, and I agree with most of them. I am a Nix person who has been a bit obsessed with package management for a long time, and it's probably fair to call me a bit of a 'container skeptic'. I used to think Flatpaks were a huge pain the butt, but over the last few years, I moved to using them for all third party software
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |