I’ve been using arch for a while now and I always used Flatpaks for proprietary software that might do some creepy shit because Flatpaks are supposed to be sandboxed (e.g. Steam). And Flatpaks always worked flawlessly OOTB for me. AUR for things I trust. I’ve read on the internet how people prefer AUR over Flatpaks. Why? And how do y’all cope with waiting for all the AUR installed packages to rebuild after every update? Alacritty takes ages to build for me. Which is why I only update the AUR installed and built applications every 2 weeks.

  • Fliegenpilzgünni@slrpnk.net
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    AUR for niche stuff, Flatpak for everything else.

    I personally prefer Flatpak because:

    • It’s simple
    • It’s the recommended way of installation for most distros, especially image based ones, like Fedora Atomic for example
    • It’s accessible for everyone more easily
    • It works most of the time

    I use the AUR in a Distrobox container for software I can’t find any other installation method. For me, it’s to cumbersome to hop into the terminal and proceed with the installation.
    For Flatpaks, it’s just one click and it’s done.

  • LeFantome@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    The AUR is the best thing about Arch. yay -Syu and everything is updated. Painless.

    I tend to use binary packages to avoid long compiles. If an update includes something that is going to take a while, I often exclude that package from the update. After everything else is updated, I can run it again to get the last package or two. They can just run in the background while I do other stuff. If it is a program I am going to use right away, I may put off the update of that package until I am done my session. This is pretty common with JetBrains updates for example.

    I do not have a single Flatpak.

  • ReallyZen@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    An AUR package has been done for Arch by (supposedly) someone who knows what they are doing and needs it on their Arch Machine

    A Flatpak is something done by someone, to (supposedly) work everywhere, untested on Arch, that may or may not work. And crash (Ardour on Asahi). Or waste hours or you life to render files incorrectly (kdenlive on arch and asahi).

    Native versions work perfectly.

    I thought I was clever in using arch/aur for everything, but pull KDE or QT apps from Flatpak to keep my gnome install a bit more tidy… For this, you’d have to have those Flataks to work, and sometimes they don’t.

  • limitedduck@awful.systems
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    Users who don’t want redundant dependencies will probably prefer AUR packages. It can also be nice to manage all the packages with just the helper app. I try to install the binaries of apps from the AUR if they’re available to avoid the long build times.