[He/Him, Nosist, Touch typist, Enthusiast, Superuser impostorist, keen-eyed humorist, endeavourOS shillist, kotlin useist, wonderful bastard, professinal pedant miser]
Stuped person says stuped things, people boom

I have trouble with using tone in my words but not interpreting tone from others’ words. Weird, isn’t it?

Formerly on kbin.social and dbzer0

  • 8 Posts
  • 49 Comments
Joined 1 year ago
Cake day: March 5th, 2024
  • Aatube@kbin.melroy.orgtoLinux@lemmy.ml•The wonderful world of Linux package managers
    13·
    2 days ago

    If you want to run post-upgrade, you got to do it yourself.

    That’s just wrong. Pacman has hooks, and easy hooks are one of the reasons Pacman is loved. In a normal weekly upgrade I see Pacman run over 30 hooks. I do not think simply not updating user-modified config files is just the bare minimum needed.

    I think this boils down to Arch’s philosophy: the users should know their system, and when something could break things, don’t assume things and do it automatically; have the user do it instead. Thus when shipping config updates to a user who had already changed their config, Arch does not overwrite the configs and instead ships the updated vanilla config with a .pacnew suffix. The user is expected to review such pacnews, a process that’s just like normal git merge conflicts when you use the pacdiff tool.

  • Aatube@kbin.melroy.orgtoLinux@lemmy.ml•The wonderful world of Linux package managers
    7·
    2 days ago

    Agreed. The normal pacman CLI does have a comparatively much higher learning curve though compared to e.g. APT. It’s not that hard to learn either but when you’re scrolling over a long-ass manpage, you do not immediately realize from the headers which whizz by in a flash that -S (alias for --sync) is for installing from repos, -Ss is for searching from repos, -S does not by itself “synchronize” with repos by pulling newest repo package metadata because well that’s not what we’re “synchronize”-ing with and you have to add the “y” flag, -Su (remember to add “y”!) is for upgrading all packages instead of -U (alias for --upgrade), and -U is for installing a local package. Compare that to the APT/dpkg system’s apt install, apt search, apt update, apt upgrade, and dpkg -i.

    Admittedly APT does need one to get behind the fact that there are different commands and that “update” and “upgrade” are different, but that’s way less to remember (especially since apt is meant to be the interface for everything a user should do) compared to remembering pacman’s interesting definitions of database, query, sync, upgrade, and maybe files, while the only definition unlikely to be guessed with APT IIRC is update vs upgrade. You’re far more likely to need a pacman cheatsheet than an apt cheatsheet.

    But in the end, let’s all love libalpm.