I’m wondering if a distro like the one I’m looking for even exists:
- simple as in KISS and vanilla. This excludes Debian where the package manager is too complex and packages deviate from upstream too much, as well as OpenSUSE, where systems administration relies on GUI tools too much and the package manager is even more complex.
- fixed release (excludes everything Arch-based)
So from the major distros, only Fedora is left as an option, where I really don’t know enough about it. Is it possible to do a minimal install of it? Is it built around a GUI app store? Does it rely on Flatpak like Ubuntu does with Snap?
Or are there other distros out there that I’m not aware of? Basically everything from the past 5 years I have no experience with. I’ve heard good things about NixOS, but it sounds weird as a daily driver.
What on God’s green flat earth are these requirements??
What about apt do you find too complex? I guess what are you defining as 'complex"?
I’m terms of package management you’ll be hard pressed to find anything that requires less work that apt, yum, zypper or their various GUIs.
Debian is the most vanilla distro you can get and you are excluding it out of the gate because of apt. So it would be helpful for all of us to understand your complexity issues with apt (and zypper).
It was my first distro and I miss it a lot. Simplicity and stability are main selling points
Preach!
Talking for myself and not OP: What’s complex about apt and yum is the package format per se. The cli is very straightforward and “just works”, but whenever you want something that’s not packaged and need to package it yourself, you gotta fasten your seatbelt and prepare for the complex task of creating an RPM or a DEB package.
I know there are tools to help with that, but I’ve created packages for many distros (Debian, CentOS, Alpine, Arch, Void and Crux), and rpm/deb are just way more complex to create than the alternatives.
This guy gets it.
How often does that happen–where you need to package your own deb or it leaving orphan meta-packages that it doesn’t remove? Or is this more of a ‘curiosity’ than hard requirement because I think ultimately the short answer to your question is: I dont think it exists as you’ve described it.
Fedora Silverblue seems like it might get close. It’s immutable OS with flatpaks that sit on top. At least that’s my understanding of it since I haven’t used it myself. I have NixOS in a VM so I could learn it and NixOS is similar in that its immutable, but its definitely complex. Its also hard to use–which is a distinction you are making in this thread as well. So I am not sure its ‘better’ than any of those others in the grand scheme of things. In my limited experience with it as a pretty advanced linux user, it would probably be a solid daily driver after you spent 2 years tuning your config to your liking. But simple things will have your tripping over yourself.
It has the learning curve of vim and the expression language is a bit annoying since its a special unique thing you have to learn. Its not exactly hard but its not intuitive either and the documentation isn’t super approachable even if everyone says its great.
One of those immutable OS’s with flatpak on top would probably be the closet I think you can get to what you are asking.
% pm -i | wc -l 55That’s how many software I packaged myself. They are installed to
/usr/localusing an alternative package manager because I couldn’t be bothered with making an appropriate .deb.And as to explain how this alternate workflow is less complex, here’s how I go about installing a program:
% git clone git://git.z3bra.org/human ~/code/human Cloning into '/home/z3bra/code/human'... remote: Enumerating objects: 53, done. remote: Counting objects: 100% (53/53), done. remote: Compressing objects: 100% (53/53), done. remote: Total 53 (delta 28), reused 0 (delta 0), pack-reused 0 Receiving objects: 100% (53/53), 9.35 KiB | 195.00 KiB/s, done. Resolving deltas: 100% (28/28), done. % cd $_ % pack CC human.c LD human install -D -m 0755 human /tmp/tmp.rfnbLyIQOz/usr/local/bin/human install -D -m 0644 human.1 /tmp/tmp.rfnbLyIQOz/usr/local/man/man1/human.1 > /tmp/human@0.3.tbz installed human (0.3) % pm -i human usr/ usr/local/ usr/local/bin/ usr/local/bin/human usr/local/man/ usr/local/man/man1/ usr/local/man/man1/human.1
What about apt do you find too complex? I guess what’s re you defining as 'complex"?
The fact that it has recommended and suggested dependencies, meta-packages and virtual packages, that installing a package ad then removing it again often leaves your system in a different state than before, that it has 7 different default front-ends for different tasks, …
Debian is the most vanilla distro you can get
Debian packages often deviate significantly from upstream.
If you say Debian’s and OpenSUSE’s package manager are too complex for you, I can tell you that NixOS’ package manager is definitely not for you.
Hannah Montana Linux.
if Hannah Montana Linux is to complicated, then Uwuntu
This is always correct.
This excludes Debian where the package manager is too complex and packages deviate from upstream too much
This isn’t even remotely true.
Also going with Debian + GNOME Software + Flatpak isn’t a bad ideia at all. Unlike Snaps, Flatpaks are fast you won’t notice delays and waste 10GB of RAM for each application you want to use. And at the end of the day you get rock solid Debian + the latest and greatest software as Flatpaks without “deviation from upstream” and you also keep a clean system.
You’ve picked pretty stupid criteria, but if you’re adamant on it, as another commenter said Slackware is probably one of the best options.
Fedora dances with Flatpak quite a bit, but you could double check if RHEL does (since that’s what Fedora is based on).
Again, while Slackware (and possibly RHEL) fit your criteria, your criteria seems pretty silly, and you’re likely to walk into bigger (and harder to solve) problems on more obscure platforms.
If apt is too complex for you, I don’t know what to tell you…
I feel like you’re confusing “hard to use” with “complex”.
Apt is extremely complex under the hood, which shows when you try to build a package for it, or install a package with many dependencies then remove it again, leaving traces behind, or when you break your system by using different front-ends (apt, apt-get, aptitude, synaptic) which are all included in the default installation, but handle dependencies differently.Most modern package managers have that level of complexity tho… That dependency tracking can take a lot of computation.
Maybe a notable exception would be Slackware package manager, but you won’t find what you’d expect from modern package manager (e.g. dependency resolving, autoremove package).
I find building packages with Gentoo to be much simpler than with Debian. Probably this is due to the fact that Gentoo users would regularly build their packages, unlike Debian.
I also learned Debian automatically generate dependency list by scanning the binaries of each package to see what dynamic libs it links. Bet that does add to the complexity by much.
Slackware. It’ll take a bit of getting used to but it meets your criteria.
I was going to say the same
I have the same recommendation, try slack out it really feets.
But I think it will be like Genie fullfiling your wishes - you don’t really know what you are looking for, but it might really suit you.
On OpenSuse, sudo zypper install package-name
Not too complex if you ask me.
complexity =/= ease of use
You complained about reliance on GUI tools, so you’re going to have to explain how that isn’t easy to use if folk are to help you. What is the issue with that for you?
Most stuff on opensuse, you can also do on command line. Having a GUI to help people who like a GUI doesn’t mean people who like command line aren’t facilitated.
How is apt too complex? And which is simple then?
It has recommended and suggested dependencies, meta-packages and virtual packages, installing a package and then removing it again often leaves your system in a different state than before, it has 7 different default front-ends that can break your system if you switch which one you use, …
Pacman and Slackpkg are examples of simple package managers.
Pacman has all of those as well.
Slackware is obvious choice, exactly what you are looking for.
It was my first distro and I miss it a lot. Simplicity and stability are main selling points.
I haven’t used it myself, and admittedly am entirely unfamiliar, but a buddy put popos on something recently and was talking about how smooth and simple it was. Might be worth a gander.
PopOS is Debian based, which has apt as a package manager (OP no likey likey).
Slackware is the solution then clearly.
Linux mint
Same package manager as Debian, isn’t it? Which OP said is too complex.
There’s also GUI package manager, if you want to use that.
Which he also mentioned he doesn’t like to depend on.
What’s the complex part about “apt” or “zypper”?
Taking apt as an example: The fact that it has recommended and suggested dependencies, meta-packages and virtual packages, that installing a package and then removing it again often leaves your system in a different state than before, that it has 7 different default front-ends for different tasks, (don’t mix them!), apt-pinning, blacklists, 5 different repository branches, …
After a hiatus in Mac and windows land, I came back into Linux a with similar wishlist.
It’s quite a diversion, but I actually went with FreeBSD. Now it’s not Linux but with the separation of base system and packages, you get a stable base that is released at a pretty fixed consistent schedule.
For packages you can pick from quarterly or weekly update schedule, so you can have a stable base OS with bleeding edge software. The binary package manager is easy to use, but if you want more control you can opt for building from source as well.
The init system is BSD based so all main config goes into a single rc.conf file, very easy to understand and work with.
Most mainstream applications such as Firefox, postgresql, nginx etc are just a
pkg installaway and it natively supports zfs (even as root fs) which was one of the reasons I got really interested in it 10 years ago.Of course, there is software, especially some younger projects that don’t support FreeBSD. So while there are thousands of packages available, some Linux only applications won’t work.
Personally, I would pick FreeBSD any time that the software I require supports it. I only run Linux (settled on pop is for now) if the software I need requires it.
Thank you for one of the few helpful answers in this thread.
