72
submitted 1 day ago* (last edited 1 day ago) by kiri@ani.social to c/linux@programming.dev

(No provocation)

I see these reasons:

  • newbie
  • lazy (don't wanna edit config files etc.)
  • unique features (like assistant/toolbox, some optimizations like in cachyos)
  • wanna check how different systems are set up (that's rather distrohopping)

Personally, I used manjaro i3 when I was beigginer and wanted to see how tiling WM should be configured (check out ranger config, for example). But after some time, I don't see reasons why not to just customize pure arch (same with debian and debian-based distros).

you are viewing a single comment's thread
view the rest of the comments
[-] Hamartiogonic@sopuli.xyz 1 points 1 day ago

LOL. Same.

Every now and then I find a comment where someone who clearly knows what they’re doing is deploying an Arch server in a work setting. Feeling confident with that decision takes something I don’t have. Maybe it’s experience, knowledge or something.

[-] victorz@lemmy.world 2 points 1 day ago

I believe there are docker images for Arch? But those probably have some form of reproducibility, I should hope. Since you can't install specific versions of packages declaratively with pacman unless you have physical access to the actual package file, I would not use it for a server. Maybe coupled with Guix or something? I dunno.

Maybe they need an environment with very up-to-date packages, or something along that vein. 🤔

[-] Hamartiogonic@sopuli.xyz 1 points 12 hours ago

Docker would be the sensible approach.

Imagine if the new version of some package is only compatible with the old version of PHP, but now Arch is using the new one. The admin would have to keep the old version of PHP until the devs of that other package release an update. I recall reading something about pacman not supporting partial upgrades like that.

[-] victorz@lemmy.world 2 points 11 hours ago

Exactly, partial upgrades are not supported. Always best to do a pacman -Syu to upgrade the entire system instead of just one package.

At least that's the case for system packages. More isolated packages don't need as much care or carry much risk of rendering a system unbootable or similar risks, but I say it's like signaling your turn when driving even if no one is around — best to just make it a habit. 🙂

this post was submitted on 17 Jun 2026
72 points (96.2% liked)

Linux

14008 readers
364 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS