[godelski]

  > Maybe I'm stupid, but they don't even have current llama.cpp, WTF?

I don't understand. It's in the AUR...

https://aur.archlinux.org/packages/llama.cpp

  > has to be compiled by yourself, either via the AUR

I don't think I'd call the AUR "compiled by yourself". It's still a package manager. You're not running the config and make commands yourself. I mean what do you want? A precompiled binary? That doesn't work very well for something like llama.cpp. You'd have to deliver a lot more with it and pin the versions of the dependencies, which will definitely result in lost performance.

Is running `yay -S llama.cpp` really that big of a deal? You're not intervening in any way different for any other package (that also aren't precompiled binaries)

[LargoLasskhyfv]

> I mean what do you want? A precompiled binary?

Yes, exactly :-)

Haven't used yay or other aur helpers so far. Maybe that's why my systems run so stable?

Should maybe look into it.

Have used Yaourt on Arch in the far past, with...errm...varying success ;->

[godelski]

  > Haven't used yay or other aur helpers so far. 
  > Have used Yaourt on Arch in the far past,

Yaourt is an aur helper?

  > Maybe that's why my systems run so stable?

Sorry?

  >>> I know my ways around Arch

Forgive me, you said this earlier and I think I misunderstood. What does this mean exactly? How long have you been using Arch? Or rather, have you used Arch the actual distro or only Arch based distros?

I guess I'm asking, have you installed the vanilla distro? Are you familiar with things like systemd-boot, partitioning, arch-chroot, mkinitcpio, and all that?

[LargoLasskhyfv]

I have used plain Arch in the past, for several years, no derivatives.

At that time there existed an AUR-helper called Yaourt, which I made heavy use of. But often in haste, sloppy. Which lead to many unnecessary clean-up actions, but no loss of system. Meanwhile I had to use other stuff, so no Arch for a while. When the need for using other stuff was gone I considered several options, like Gentoo, but naa, I don't wanna compile anymore!1!! (Yes, Yes, I know they serve binpkgs now, but would they have my preferred USE-flags?) Maybe Debian, which can be fucking fast when run in RAM like Antix, but I had that for a while, and while it's usable, Debian as such is bizarre.

Anything Redhat? No thanks. SuSe? Same. So I came across CachyOS, and continued to use that, from the first "test-installation" running to this day, because it works for me, like I wrote before. Like a dream come true.

Remembering my experiences with Yaourt I abstained from using the AUR. And that worked very well for me, so far. Also the Gentoo-like 'ricing' comes for free with their heavily optimized binary packages, without compromising stability.

> I guess I'm asking, have you installed the vanilla distro? Are you familiar with things like systemd-boot, partitioning, arch-chroot, mkinitcpio, and all that?

Yes.

Are we clear now?

Edit: I'm so overconfident I'm even considering disabling the pacman-hooks into BTRFS-snapshots, because I never needed them.

No rollback necessary, ever, so far. Same goes for pacman cache. After every -Syu follows an immediate -Scc.

Because the only way is forwaaaaard ;-)

[godelski]

I've used Yaourt too. Things are a lot better these days. Yay is the standard. But I think the biggest help of helpers is updating.

Yes, we're clear now, but are you surprised by my hesitation? Because having that experience would imply you've had a lot of experience compiling things the long way. Running makepkg -si isn't that complicated. It's as easy as it gets. There's no make, no configure, no cmake, no determining the dependencies yourself and installing those yourself too. I don't get the issue. Take too long? Not happen automatically?

  > I'm so overconfident I'm even considering disabling the pacman-hooks into BTRFS-snapshots, because I never needed them.

lol yeah I'm sure they're not needed. Not hard to recover usually and yeah I agree, things are stable these days. I can't remember the last time I needed to chroot (other than an nspawn). I only snapshot data I care about these days and it's usually backed up remotely too. I've learned my lesson the hard way too many times lol.

[LargoLasskhyfv]

> I don't get the issue. Take too long? Not happen automatically?

Yes and Yes. Long before Arch I did LFS and Gentoo. And NetBSD like Gentoo.

I'm having had it! Gimme binaries in the flavors (Hello OpenBSD!) I want/like!1!! ;->

[godelski]

  >> Not happen automatically?
  > Yes

I got you fam

  # /etc/systemd/system/pacman_auto_update.timer
  [Unit]
  Description=Update automatically because ain't nobody got time for that
  Documentation=man:pacman(8)
  
  [Timer]
  OnCalendar=weekly
  Persistent=true
  # Optionally wake system up to upgrade
  #WakeSystem=true
  
  [Install]
  WantedBy=timers.target
  After=network-online.target

  # /etc/systemd/system/pacman_auto_update.service
  [Unit]
  Description=Update automatically because ain't nobody got time for that
  Documentation=man:pacman(8)

  [Service]
  Type=simple
  ExecStart=/usr/bin/pacman -Syu --noconfirm

Joking aside, I do use a version of this except I just run -Sy and I do it daily. I find it does help speed things up.

  > Gimme binaries

Definitely not going to happen on Arch and this runs completely counter to what you claimed to like about CachyOS. Distributing binaries is not going to result in a very optimal system... Which is what caused those red flags to be raised in the first place

  >>> After every -Syu follows an immediate -Scc

Btw, I don't suggest doing this. If an update breaks your system then you don't have the versions cached to roll back to. I mean you can download again but your cache gives you a good hint at what did in fact work.