My take on "not being defined by a package manager" - The end user should not give a crap what is under the hood. What is / is not in repository is another matter entirely.
If Solus switched to using apt
tomorrow that alone does not magically make it compatible, because unlike Ubuntu, Solus is not based on Debian and is a rolling release. Base on something else and inherit a lot of their decisions at which point I start to question why it needs to exist at all.
casablanker It's just that if the package manager is going to be a stumbling block for me, I would rather know now and move on....
I guess what I'm asking is what the experiences have been with seasoned Solus users, using the eopkg system. Especially if like me you come from an APT background. Is software easy to find? what do you do if software is not in one of the repositories? compile manually?
I've been using Linux since the late 90s, most of my experience in Linux comes from working in IT. I've tried most distributions you are likely to have heard of and many you probably haven't but Solus is the one that made me get rid of Windows completely on my home systems. I've been using Solus for at least 2y 42w 1d
(How long my IRC handle has been registered). If something is not in the repository I use universal packages such as snap/flatpak/appimage or compile it myself. Currently I use two things not in the repository. spotify
(snap, technically also in the 3rd party section of the software center but I prefer snap over that) and barrier
(compiled and packaged myself, it has been accepted into the repository I just need to submit it).
But ultimately I don't make decisions based purely on what if scenarios, I can't tell you what bests suits you and I can't tell the future so good luck.