flatpak remote-add flathub-verified --subset=verified https://dl.flathub.org/repo/flathub.flatpakrepo
    • rollingflower@lemmy.kde.socialOPDeutsch
      1·
      3 months ago

      The Arch repos, being quick, rolling, not restricted legally or being upstream of some corpo distro like Fedora or OpenSUSE etc

      Idk ask Steam?

    • ManniSturgis@lemmy.zip
      11·
      3 months ago

      I just want new packages and Tumbleweed sucks, and don’t even get me started on Fedora and their codec nonsense. Every time I tried Fedora I run into issues. You can’t even use their packaged version of VLC cause they don’t also package the correct version of ffmpeg. Fedora is a joke. Nobara even worse cause that one is outdated on top of it. Arch is the way and you are all wrong.

      • jbk@discuss.tchncs.de
        1·
        3 months ago

        Thank software patents for the codec trouble, not Fedora / Red Hat. They just don’t want to get their asses sued for free software

        Anyway I can use VLC and ffmpeg just fine with RPMFusion, idk what ur issue is, but judging by that

        you are all wrong

        i probably just wasted my time on a brainless troll like you.

        • ManniSturgis@lemmy.zip
          0·
          3 months ago

          They just don’t want to get their asses sued for free software

          How come the other distros don’t seem to care? Does it just come down to them being based in the US?. They can’t be the only distro mainly based in the US, can they? VLC would not play ANYTHING. That was installed from RPMFusion in Fedora Kinoite 39. But even IF it were to work, this whole RPMFusion thing is ridiculous. If I had to install a bunch of codecs and drivers from the AUR I would say the same about Arch. That would absolutely kill the distro for me.

          i probably just wasted my time on a brainless troll like you.

          Hard to argue with that ;)

            • 737@lemmy.blahaj.zone
              1·
              3 months ago

              It’s an issue with zypper, if you ever updated your device, you did encounter it. Maybe you have never seen how fast Arch updates are in comparison.

              • Petter1@lemm.ee
                1·
                3 months ago

                Well my arch machine, I update using yay, and speed it takes differs depending on how long I haven’t use that PC. On my TW PC I don’t know the time it needs, since it does it automatically when I turn off the PC…

        • ManniSturgis@lemmy.zip
          01·
          3 months ago

          Eh, just my personal opinion. I tried it once and didn’t like it. But I can admit that is similar to me saying “Gnome sucks”. It’s obviously a matter of personal opinion.

  • infeeeee@lemm.ee
    2·
    3 months ago

    If an AUR package wants to install 137 python dependencies, I usually search for a flatpak instead.

      • Fatih Özsoy@mastodon.social
        1·
        3 months ago

        @pineapplelover @infeeeee No, some people just don’t want to install tons of packages just for an application they want to use to. The more package means the higher chance for system breakage. It’s better checking dependencies and pkgbuild before install

    • Petter1@lemm.ee
      0·
      3 months ago

      You can remove dependencies after install, at least in yay, I never do tho.

      • infeeeee@lemm.ee
        1·
        3 months ago

        That’s install dependencies (in PKGBUILD they are called makedepends), python programs usually need them for runtime (depends in PKGBUILD). On the main page of a package they are listed together, but on the PKGBUILD they are separate

    • rollingflower@lemmy.kde.socialOPDeutsch
      23·
      3 months ago

      Fair point. But when apps are on Flathub and people say “I dont care I have the AUR” they need to know.

      • the AUR has no verification at all
      • the apps have no permission system at all, so you need to trust them 100%
      • they are installed on your system and might mess up updates, give dependency errors etc.
      • their solution does not apply to nontechnical people. If a solution is not scaleable, it is not a good solution
      • Skyflare@discuss.tchncs.de
        4·
        3 months ago

        All you need to verify an AUR package is to read the PKGBUILD file, which is something the AUR keeps on encouraging you to do (this assumes that you trust the upstream repo, which is something that even official packagers of most distros do)

        Also a lot of flatpak packages aren’t sand boxed enough to be safe and only ends up giving false sense of security to nontechnical users

        Your last point is extremely important though, AUR is horrible for nontechnical users (which is why the AUR discourages AUR helpers)

        • rollingflower@lemmy.kde.socialOPDeutsch
          2·
          3 months ago

          Okay having an easily readable build file is a bit missing. Flathub hides that a lot.

          I think their rating system, which is on the website and also GNOME Software, displays apps with home access as insecure.

          And somehow this seems to be general knowledge and an issue about a privilege escalation through a local override was just closed. Yay

  • PINKeHamton@lemmy.blahaj.zone
    21·
    3 months ago

    I have just had bad experiences with flatpack so I don’t want to use it and the aur has the stuff I need and flatpack dose not

    • taanegl@lemmy.world
      2·
      3 months ago

      I’ve had nothing but good experiences with Flatpaks/Flathub and bad experiences with AUR/nixpkgs.

      Fedora also has it’s own Flatpak repo now with it’s own runtime.

      • rollingflower@lemmy.kde.socialOPDeutsch
        2·
        3 months ago

        Same. Ubuntu AND Fedora Libreoffice, SciDAVis and more where broken, not the Flatpaks.

        Flatpak is really meant for the big GUI apps. No problem with small distro packages really. It just takes off the huge burdens of maintaining distro packages for like Libreoffice, which is as big as the Linux Kernel.

    • rollingflower@lemmy.kde.socialOPDeutsch
      11·
      3 months ago

      You need to be more specific.

      You need to think about the background problem here.

      When Google made Android, it was web based. Their “perfect sandbox” ironically has no internet toggle. They won tons of marketshare, and iOS is not different here, both restrict apps to containers and have permission systems to reach out of these containers to access sensors, files and other data.

      Desktop operating systems are way older and have no such concept. We have mandatory access control with SELinux and Apparmor, but those are (I think) more complicated than Flatpak.

      Flatpak is a solution for multiple problems of Desktop Linux Apps at once.

      1. isolate apps with a real permission system
      2. make apps run anywhere
      3. have a single platform to target, so we dont need packagers anymore (for most GUI apps) and can file bugs upstream
      4. separating apps from the system: stable distros can have modern apps (similar to Windows) and Apps dont affect the stability of the OS at all. Also config files of such apps are in their container, not bloating your “oh so good xdg basedir”

      These are all extremely important points for a healthy, modern and secure Linux Desktop.

      But there are also issues to every point:

      1. most apps are not adapted to this model, which means they need broad static permissions like Pulseaudio, home or even host, allowing surveillance or trivial (even documented) privilege escalation. This is basically how apps like Flatseal work. Pulseaudio has no portal, do apps can listen to your mic whenever they want.
      2. Apps that “run everywhere” will not have distro-specific optimizations. The system needs to run on old LTS kernels to be universal, which means you miss out on tons of optimizations. Developers could just not care, but this depends on the app.
      3. Flatpak is more complicated than Snap (or even Appimage, if you leave the manual signing, monitoring vulnerable libraries and having a manual repo out). So it is not a great experience for “the Linux packaging model”. GNOME Builder is a good IDE for it but afaik only for GTK apps.
      4. No issues here. This is the core princible of “immutable” distros like Fedora Atomic Desktops.

      If you have issues with flatpaks, you need to be more specific. Maybe it is a packaging issue, or you expect an app to do stuff that is not