As someone who used Gentoo for over a decade, including in production environments - I disagree.

Its a falsehood pushed by old 80's thinking. It sounds nice, in theory.

In practice, what you often get are bugfix patches blindly applied to older codebases, oftentimes by people (distro maintainers) who are not very familiar with the codebase. As long as the patch applies, and it passes various tests.

Remember, most OSS projects - including some critical ones - do not have large teams of devs able to maintain multiple codelines in tandem. Usually, the dev(s) just work on the latest, and pay only cursory attention to applying security bugfixes to older versions.

After all, how is an OSS dev for proj X meant to know (or even give a damn for) which distro arbitrarily decided which older version is somehow the SECURE and BLESSED one.

The dev in question probably moved on from that version months (and in regard to Debian, probably YEARS) ago.

So in theory, what you said sounds right. In practice, no.

I’ve also run Gentoo in production. But you have to know what you’re doing more than with, say, Debian or CentOS (RIP)

Gentoo is usable in production. Straps out extras. Only thing there is what you put there.

Seen it done and participated.

Production case study: ChromeOS is based on Gentoo.

I've also known a couple shops that run Gentoo as their distribution. Usually a central binary package host / build machine which makes it very easy to have a set of staging hosts. Just test package releases like normal before migrating them to prod.

Gentoo is perfect for proper systems engineering: Create a profile, and then manage what goes into it, in exactly the same way as you describe on Debian.

Actually, you don't have to do a full system upgrade, you can update a single package.

People have used Arch in prod. But personally I'll still use Debian to be on the safe side despite all of the issues that comes with.

Just because it often works doesn't mean it's a good idea. Updating a single package is officially unsupported [0] and it's burned me personally on a number of occasions.

[0] https://wiki.archlinux.org/title/System_maintenance#Partial_...

The context of the original comment is that you're updating that package on a test server and then testing it.

But sure, just yoloing a single package upgrade can break things, obviously.

Just because it isn't your good idea doesn't mean it's a bad idea.

I expect that's why they mentioned that it's officially unsupported behaviour. That doesn't seem too relevant to whose idea it was.

weel it's a bad idea unless you update just one package that doesn't have too many shared dependencies, things gets complicated with shared dependencies across their packages, so that's why it's better to run the full -Syu of course not automated but when you know what you are upgrading and possible manual interventions (if any) or caveats that you might have with the changes.

> Like Gentoo it's one of those OSs that is cool for linux nerds and a headache for people who actually need to practice proper systems engineering.

Fear not. As GKE is running on Container-Optimized OS which is based on Chromium OS which itself is based on Gentoo, you can safely practice proper systems engineering within the container environment :)