Once I went travelling and left my arch(btw) desktop computer unplugged for just over a full month.
When I came back there were 1 235 packages needing updating, between repo and AUR.
… It worked fine tho. That install didn’t really go to shit until about a month ago, when months of sloppy system management on my end finally caught up to me and left me with a lot of mysterious issues. So I cut my losses and ditched it.
Yeah, I ran Arch for years and every time the wiki or someone in irc said, “Do it X way, not Y,” I always followed that instruction. Never had a single issue with system stability.
Guess that’s atypical? I learned a lot, these days I mostly use Ubuntu or Debian.
Tbh, trusting pacman with everything and keeping my AUR pkg sources preserved in a source folder is literally all it took to keep the system stable. Idk, is that a lot? It felt easy.
Well, prepare for some even bigger updates. When a new libc or gcc or similar such version comes out, they like to recompile everything.
Sometimes you get 4000+ package updates, just from one day to the next.
They do that, though, because it increases compatibility, and you get automatic snapshots, too, so it’s kind of less daunting than 250+ package updates on Debian et al.
I haven’t personally had those huge updates ever break on Tumbleweed. The one thing that apparently caused stuff to break was the recent KDE 6 update, but I’ve heard so and did it with Discover’s offline update and it all went fine.
Once I went travelling and left my arch(btw) desktop computer unplugged for just over a full month.
When I came back there were 1 235 packages needing updating, between repo and AUR.
… It worked fine tho. That install didn’t really go to shit until about a month ago, when months of sloppy system management on my end finally caught up to me and left me with a lot of mysterious issues. So I cut my losses and ditched it.
I’m using OpenSUSE Tumbleweed now (btw).
I wonder why people don’t say : I don’t use Arch BTW… ?
skill issue
Yeah, I ran Arch for years and every time the wiki or someone in irc said, “Do it X way, not Y,” I always followed that instruction. Never had a single issue with system stability.
Guess that’s atypical? I learned a lot, these days I mostly use Ubuntu or Debian.
Tbh, trusting pacman with everything and keeping my AUR pkg sources preserved in a source folder is literally all it took to keep the system stable. Idk, is that a lot? It felt easy.
Well, prepare for some even bigger updates. When a new libc or gcc or similar such version comes out, they like to recompile everything.
Sometimes you get 4000+ package updates, just from one day to the next.
They do that, though, because it increases compatibility, and you get automatic snapshots, too, so it’s kind of less daunting than 250+ package updates on Debian et al.
I haven’t personally had those huge updates ever break on Tumbleweed. The one thing that apparently caused stuff to break was the recent KDE 6 update, but I’ve heard so and did it with Discover’s offline update and it all went fine.
Tumbleweed rebuild the entire repo after the xz-utils thing, I had like 5500 to update