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!! ;->
>> 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.I'm perfectly at ease with initiating them manually, as I see fit.
For me that means automatically tracking dependencies of things like USE-flags in Gentoo's Portage, or Exherbo's Paludis.
And the possibly resulting conflicts. Arch and its makepkg and the stuff in the AUR has simply no provisions(that I'm aware of) for that. It's all manual, IMO. AUR-helper, or not.
> 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
Says you. I counter that with my years long experience(on CachyOS), limited to the stuff they DO deliver as binary. Obviously carefully tested by people who really know what they do, on much faster systems than I have, before delivery to the general public.
> 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.
Never needed it, neither on plain Arch in the far past, nor the two years of CachyOS now. Should something bad happen I can boot some rescue-image from whereever, and fix it that way. It's just a waste of space.
Edit: Please don't suggest Nix(OS) or Guix. They give a shit about optimization in the name of 'reproducible builds', and go for the lowest common denominator because of that. Which is understandable, given their goals. But they are unaligned with mine.
Closing all other apps, terms, filemanagers. Klicking restart. Hands off. Very quiet and fast boot. Sddm appears. Login. Plasma is there. FF reloads as it should. Everything else works.
So Yay!?
(Squeekily screaming: *Oh my gawd!1!! Nao my (almost) pristine binary system iz tainted!1!!*)
You were saying?
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?
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.