45
CachyOS August 2025 Release — CachyOS (cachyos.org)
submitted 1 year ago by to c/linux@programming.dev
17 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 10 points 1 year ago* (last edited 1 year ago) (7 children)

Arch is stable until it isn't. Unlike LTS distros, you generally will want to check the Arch/cachyOS website or forum before updating to catch any potential system breaking bugs to either wait until they're fixed, or apply a workaround found by the community in the forums. As long as you do that, you can generally avoid problems, but it is an extra step that something like Debian or Mint generally doesn't require.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 2 points 1 year ago (3 children)

    I don't know what the time frame or interval of these events is. I switched to CachyOS 5+ months ago now, updated in the evening before going to bed (basically daily, bleeding edge as you might say).

    I had zero issues. Maybe it'll be an issue one day. But while I could check for any critical known issues, and that would be an extra step (I don't, so it's not), it has saved me so much time just having up to date packages on literally everything just in the repo. It's insane compared to especially Debian, where things can be years behind and the only way to get a reasonable recent version is to build from source, find a .deb repo for it or install a manually downloaded package directly (like on Windows).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 1 year ago (2 children)

    It's fairly random when a problem pops up. You could be fine for another 6 months to a year, but generally the possibility is there every update.

    As for getting updated software, I've personally been able to get the latest versions of all the apps I use on Debian thanks to flatpak, which is as simple as adding the flathub repo.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    I fundamentally dislike the concept of flatpacks. It's fine and/or necessary for immutable distros, but I see little point in loading every dependency individually for every app. It's fine for an app or two, but adds up to a lot relatively quickly when used as the default system. To each their own I guess, but I'm very happy with the ecosystem of the huge, up-to-date native repo + availability of the AUR.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 1 year ago*

    I can't say I've ever actually witnessed those things presenting as a problem on my system, personally.

    One advantage (imo) of flatpak over the AUR at least, is that flatpaks can have a verified status, which makes them as safe as using a distro package (sometimes more so, since they can be sandboxed), where as each AUR package should be manually inspected to avoid the potential for malware, as recently occurred on there. Without knowledge on what to look for in an AUR build script, it can be a potentially unsafe source.

    Debian + Verified flatpaks offers good security for the widest range of packages for the least effort, at least in my experience.

  • permalink
  • fedilink
  • source
  • parent