a young man from a far away land.
corposlave (“software engineering consultant” lol).
GNU/Linux (Slackware). Programming (asm, C, sh, Lisp, Lua, Web, JS, etc.). Likes writing documentation, understanding & maintaining systems, archiving, organization. Interested in paper machines, books, visual novels, writing, drawing, anime. EN/AR fluent, TR can order food, JP early learnings.
RƎD.
@that_leaflet@lemmy.world Slackware is the closest I know. It has a set of packages that it considers the official distribution, and you’re supposed to install all of them unless you know what you’re doing, and it doesn’t provide any more extra packages to choose and install; anything else you might need that’s not in the default install, you install from a ports-like community repo called SlackBuilds.org, or other providers of SlackBuild scripts or pre-built packages. To update the entire core system, you run slackpkg update && slackpkg upgrade-all. It will only upgrade Slackware’s core packages, and not your extra packages. If you’re running a stable Slackware version, then those upgrades have very little chance of breaking your dependent extra packages. If you want to upgrade your extra packages, then that’s on you, whether you’re doing it manually, or using one of the many community-made non-official package manager. This setup has been very stable in my commercial production experience which started with Slackware 15.0.