Are you saying you've had your PAM config broken by a package update when you didn't update anything in /etc, or that you had your PAM config broken by a package update where you blindly accepted changes to stuff in /etc?

Exactly the same is true for me.

I would suggest Calculate Linux.

It's 100% Gentoo, with additional customization (e.g. profiles presetting not just sane defaults, but also things you usually want on desktop [e.g. samba, network printers ...]), there are pre built binaries for all profiles and basically all the software (but you can still override some and get it compiled with or without specific features) ...

And perhaps most importantly - there's extra tooling/automation around the Gentoo/portage updates and such.

With vanilla Gentoo - beyond regular PITA to update packages due to various package/use-flags conflicts (which would make me do it even less often). I was also regularly (every few years) having to reinstall Gentoo because my glibc/bintools/python/etc were so far behind that during system update something would break and fixing it was basically reinstalling Gentoo from stage3 tarball.

It's been ~10 years that I've "switched" to Calculate Linux - and it's "cl-update" was automatically solving even those things that would've left me with world update broken system.

if you did not want a high maintenance distro why choose Arch? Its meant for the opposite of a Mac user - people who want to control everything, vs people who want it all taken care of for them. There are lots of things in the middle.

> I don’t have time to futz around installing Linux distros instead of getting laid like I did as a teenager.

Install one and resist the temptation to distro-hop. Even better, buy a machine with Linux preinstalled.

Before I switched, I did really like the piracy scene. Soundsource, the software you mentioned, was definitely one of the first I got.

Now, I think there's an open source MacOS volume manager thing.

Edit. I think it's this: https://github.com/ronitsingh10/FineTune

Good news! These days, you can just buy a computer with Linux preinstalled, with support!

Just leave the distro it shipped with alone and live your life.

That's unique to the Gentoo model and gives a fine-tuned system with virtually zero bloat. Other distros inevitably pull in dependencies you don't need because they are linked at build-time in case someone relies on it; choices like crypto backend are made for you by the packager.

Guix lets you tweak things on a per-package level, but currently offers no global feature flags. You can do wild stuff like replace OpenSSL with LibreSSL everywhere, but only as long as they are API- or ABI-compatible.

There's already tooling for using say .deb or golang packages - but still having them installed as proper Gentoo/portage ones.

PS. Tek sada videh korisničko

And still benefit from packages/system being smaller/faster because they are not built to cater for all possibilities.

And you can still override options (use flags) and compile some things exactly as you want/need them.

Most bashisms are very old and they come from ksh. Bash has added very few features beyond what was already quasi-standard in UNIX shells.

POSIX has standardized a shell variant that had already been obsolete for a long time.

The scripts that use the additional facilities added by ksh and also a few added by zsh, which now are all available in bash, can be written in a way that makes them more concise, more clear and less prone to bugs.

I believe that bash must be considered the standard for shell scripts, not the POSIX shell, which has been obsolete for more than 3 decades, i.e. since long before the existence of the POSIX standard.

When using a POSIX shell, there are many unavoidable things that can be performed only by invoking external command line utilities, instead of using intrinsic shell features. This not only can make the script much slower, but it adds extra software package dependencies, instead of avoiding such dependencies, which is the declared purpose of using a POSIX shell.

Making your shell script dependent on the existence of bash is less risky than making it dependent on the existence of awk, which may be forced when using a POSIX shell. (The existence of awk is mandated by POSIX, but there are plenty of Linux systems that do not have installed all the POSIX utilities, but they have bash.)

It is true that bash is ubiquitous only on Linux, while on *BSD it is optional. I have used FreeBSD and other *BSD systems for as many decades as I have used Linux. My first action when installing a *BSD system, after the base system is installed, has always been to install bash. I believe that whoever does not do this is mistaken and they should not demand to receive scripts that can be run without having installed one of the bash, ksh or zsh shells.

I don't really care about it being a replacement overall. I just want my own emerge command to be faster. I can't believe it's not instant like it should be.

Of course, nowadays there is little resemblance between portage and the FreeBSD ports, after a few decades of separate evolution.

When I switched to Gentoo (in 2003), among the Linux distributions (after previously using many others, like Slackware, Redhat, Suse, Mandrake etc.), I had already used for many years (since around 1995) the FreeBSD ports, so this was what attracted me to Gentoo, its software package system and its documentation, both of which had a level of quality comparable with FreeBSD and much superior to what the other Linux distributions provided at that time.

Except there's Chimera Linux now (not related to chimeraOS) and I dare say its got the fastest package manager of all operating systems with a package manager.