Subj : Arch btw
To   : Accession
From : DaiTengu
Date : Tue Nov 25 2025 14:50:55

  Re: Arch btw
  By: Accession to DaiTengu on Tue Nov 25 2025 11:14 am

 >>> I suppose it might be possible to keep up with Archlinux with the unstable
 >>> branch, but then you're just asking for trouble. ;)

 >> I've been running my devbox with ACCEPT_KEYWORDS="~amd64" for a decade. the
 >> only time I run into issues is if I haven't updated it in a couple months.

 Ac> To be honest, remembering back when I ran it, I think it was the same
 Ac> scenario where I ran into issues. If you're going to be running the
 Ac> "~amd64" branch, you should probably stay on top of things a bit better.
 Ac> ;)

 it's not really a "branch" it just tells portage to unmask packages with that flag set. 

I just checked, the latest ebuild for gentoo-sources (the kernel) is 6.17.9, which was released yesterday.  There is also vanilla-sources which is an ebuild of the kernel without any gentoo specific things added/patched. 

frequently updated are pf-sources (with popular patchsets), rt-sources (uses the PREMPT_RT patch. it was far more popular with single-threaded CPUs), zen-sources (with patches and features for desktop systems), and git-sources, which is a daily snapshot of the kernel development tree from github.

Most of the issues I run into when I haven't updated in awhile are python related, where some packages still expect an older version, and that's being replaced with something newer. 


Also, I run openrc for my init system.  systemd can rot in hell. 

(NetworkManager can also rot in hell, but that's an entirely different gripe)

....Birth is the beginning of death.
--- SBBSecho 3.32-Linux
 * Origin: The Sport is War, Total War - warensemble.com (46:1/193)

.