• 411 Posts
  • 366 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle







  • Then as a grown adult, you can make your chrome policy.json to disable the automatic updates.

    And being an adult has nothing to do with it. If left to their own devices, most people will simply not update. Some people actively resist updates. Linux Mint had some statistics that showed that like half of their users were running severely out of date versions, so they had to change things.






  • Depends on your distro.

    Like on Debian, they have meta packages where the gnome desktop meta package will most likely be updated to include Papers and Showtime, so those will get installed if you have the meta package installed. But typically they will keep the old apps around too since users may expect to have them still.

    But Flatpak has so such mechanism to do that. Distros would have to install that stuff manually as part of an update script. But they did recently introduce a way to define which apps should be preinstalled, which should help in the future.















  • The ffmpeg from Flathub is a “runtime” package, intended to be used by other flatpak apps. It’s not meant for CLI use.

    Flatpak apps are not added to your $PATH. They’re run with flatpak run appID. Though again, ffmpeg is not an app so it cannot be run this way. Though technically you could use it for CLI use by doing something like flatpak run --command=sh org.mozilla.firefox. This will open a shell inside the flatpak environment, which can use the ffmpeg flatpak runtime.

    Though now that I think about it, it would be fun to create my own flatpak package for ffmpeg for CLI use. Should be pretty simple, it would just be a mostly empty package that relies on the ffmpeg-full flatpak runtime.










  • You’re just adding arguments on arguments that aren’t making any sense now. You’re original comment and understanding has been addressed.

    My main point is that I’m worried about additional complexity. On most atomic distros, you’re not supposed to touch the base system, so various tools are preinstalled or available: flatpak, podman, homebrew, snap, appimages, systemd sysext.

    The BSDs seem to enjoy a separation of OS and user packages with reduced complexity. Though their task is easier since they are complete operating systems, whereas linux is just a kernel and many different projects put together, and many different groups putting out their own distros with varying packages and compatibility.

    Both RPM and dpkg support being able to unpackaged or install packages into your local home directory

    These don’t seem to be advertised features. More like hacky workarounds. Complex rpm commands. Ubuntu thread with various proposed solutions.

    It would be really cool if dnf and apt got good, easy, simple support for installing packages into the home folder. But that’s not what’s happening. The proposed solution seems to be systemd sysext, which again, prompted me to have worries about complexities about how software is being managed on more “modern” distributions.

    You’re just adding arguments on arguments that aren’t making any sense now. You’re original comment and understanding has been addressed

    And I keep discussing it because I enjoy doing so.



  • Thats not what I’m saying.

    My first point is that homebrew is only good for CLI applications. Almost no GUI apps are available, the only one I know of is xeyes.

    My second point is that homebrew is unsanboxed. That’s good for programs that don’t work well sandboxed, such as fetch tools like fastfetch.

    This leaves a gap of a good supported way to install GUI apps that are unsandboxed. I used to need this when I used an Android phone with a custom OS. I needed to have unsandboxed Chromium with adb tools to flash and update the OS. However, when sandboxed, Chromium doesn’t have access to adb tools.