I haven’t used any of the 3, but from a look over them superfile looks a lot more user friendly and has a nicer overall look.
Edit; the install process is rough though, complains about missing glibc but searching for that package in apt doesn’t show anything promising. It also seems to require some kind of third party font that isn’t included? I gave up lol that’s too much for me to deal with.
It’s definitely a big learning curve with how complex installing things on linux is haha, I’m still used to windows just open the exe installer and that’s it.
Yeah I hear that. I will say aptitude made my life a lot easier in terms of installing things with its recommended fixes. Also good software documentation should have a “Getting Started” section that gives you step by step instructions for each OS/Distro of how to install it. If it doesn’t… Well maybe that software isn’t worth installing anyway 🤷♂️
I mean there’s that, but it’s a lot of work for a dev too.
I would rather Linux just be able to detect what’s missing and install it for me. In the case of a lot of missing components, what it says is missing will be named completely different from the package you need to install which makes it really hard.
It was always nice with windows installers because they would come with the needed components, or windows would just prompt to install them automatically.
I would rather Linux just be able to detect what’s missing and install it for me. In the case of a lot of missing components, what it says is missing will be named completely different from the package you need to install which makes it really hard.
That does happen, but Linux doesn’t have anything to do with installing packages, your package manager does. If this package was installed through apt for example, it would also download all of the dependencies. But this package is using a makefile to build and install, therefore it has nothing to do with your package manager.
Tldr: use the package manager, and don’t use DIY packages if you don’t want to DIY
Additional package managers like flatpak and nix solve different issues:
dependency mismatch: let’s say libreoffice and this package require a different version of glibc -> flatpak downloads both versions and symlinks them in a different location in order for each package to have the correct version while not impacting your system and the glibc your DE is using
newer packages: Debian freezes packages for 2+ years, flatpak gives you a fresh version
easier packaging for developers: you can package for flatpak instead of having to maintain packages for every popular package manager and distro
That’s what aptitude does. It says “these things are dependencies that are missing. Do you want to install them?” And you can say yes, no, or ask it to try to find a different fix. And idk what you mean by that’s a lot of work. If a dev can’t be bothered to tell people how to install their program then idk how they expect people to use their software.
There are two specific problems I see here for the mentioned binaries.
The software is packaged as a generic archive, no format like rpm or deb the system package manager could/does handle. Thus, the package manager of your system does neither know that you’ve installed this binary nor what it depends on. The developer could have at least mentioned on which exact system the Linux binaries are supposed to work, e.g. Ubuntu 22.04, so that the user knows, that they might have issues running it on a different system.
The developer could have built and packed it in a way that it can be installed by the package manager of a specific distribution. Launchpad or OBS are made for this purpose. The other option, wrapping it as a flatpak, works too, but may bloat the system of the user as different versions of the same libraries are installed (system generic + flatpak version).
Nonetheless, as a Linux user, you are encouraged to build directly from source.
I had to install Golang and build it myself to make it work with my version of glibc. But in the end the themes aren’t rendered properly. In other words, proper Linux experience.
What’s the big selling point compared to
rangeroryazi?It’s pretty fancy.
I like fancy
I haven’t used any of the 3, but from a look over them superfile looks a lot more user friendly and has a nicer overall look.
Edit; the install process is rough though, complains about missing glibc but searching for that package in apt doesn’t show anything promising. It also seems to require some kind of third party font that isn’t included? I gave up lol that’s too much for me to deal with.
Glibc is the gnu c library. You wouldn’t just download that from apt. I’m surprised your Linux distro doesn’t already have that installed.
Could be a (too) old version if you’re still on the Ubuntu 22.04 base
It’s definitely a big learning curve with how complex installing things on linux is haha, I’m still used to windows just open the exe installer and that’s it.
Yeah I hear that. I will say aptitude made my life a lot easier in terms of installing things with its recommended fixes. Also good software documentation should have a “Getting Started” section that gives you step by step instructions for each OS/Distro of how to install it. If it doesn’t… Well maybe that software isn’t worth installing anyway 🤷♂️
I mean there’s that, but it’s a lot of work for a dev too.
I would rather Linux just be able to detect what’s missing and install it for me. In the case of a lot of missing components, what it says is missing will be named completely different from the package you need to install which makes it really hard.
It was always nice with windows installers because they would come with the needed components, or windows would just prompt to install them automatically.
I guess that’s essentially what Flatpak solves!
That does happen, but Linux doesn’t have anything to do with installing packages, your package manager does. If this package was installed through apt for example, it would also download all of the dependencies. But this package is using a makefile to build and install, therefore it has nothing to do with your package manager.
Tldr: use the package manager, and don’t use DIY packages if you don’t want to DIY
Additional package managers like flatpak and nix solve different issues:
dependency mismatch: let’s say libreoffice and this package require a different version of glibc -> flatpak downloads both versions and symlinks them in a different location in order for each package to have the correct version while not impacting your system and the glibc your DE is using
newer packages: Debian freezes packages for 2+ years, flatpak gives you a fresh version
easier packaging for developers: you can package for flatpak instead of having to maintain packages for every popular package manager and distro
That’s what aptitude does. It says “these things are dependencies that are missing. Do you want to install them?” And you can say yes, no, or ask it to try to find a different fix. And idk what you mean by that’s a lot of work. If a dev can’t be bothered to tell people how to install their program then idk how they expect people to use their software.
There are two specific problems I see here for the mentioned binaries.
rpmordebthe system package manager could/does handle. Thus, the package manager of your system does neither know that you’ve installed this binary nor what it depends on. The developer could have at least mentioned on which exact system the Linux binaries are supposed to work, e.g. Ubuntu 22.04, so that the user knows, that they might have issues running it on a different system.Nonetheless, as a Linux user, you are encouraged to build directly from source.
Yeah screw that lol, I want my OS to just work and be easy to use with minimal fuss.
It depends on the distro which release is installed and available. So certainly the problem is, the required and installed glibc library do not match.
I had to install Golang and build it myself to make it work with my version of glibc. But in the end the themes aren’t rendered properly. In other words, proper Linux experience.
Seems it’s been reported https://github.com/MHNightCat/superfile/issues/96a, and the PR to fix it looks like it was merged, so you should be able to run it soon
Or nnn for that matter. I will test it anyway.