I know there are ways to install software outside of aptitude on debian/ubuntu, (add repo, or build, or download binary, or possibly flatpak/snap/etc).
But being able to download *.deb files was one of the nicest aspect of using a debian based distros and now I’m seeing more and more projects include all distros except deb files.
Someone correct me but I vaguely recall that distributing debs is no longer recommended by debian itself?
- Am I wrong, and have I only co-incidentally stumbled on projects that don’t distribute debs?
- I am right and this seems like a mis-step, removing one of the most beginner friendly features that helped propagate debian based distros?
Flamesuit on.
@socphoenix Until you need two versions of Python because… reasons. When building software it also becomes a hassle: You must have the specific dynamically linked environment or your binary is useless. Solutions are either statically linked builds or containers, flatpaks, etc… Containers can cache dependencies as layers to preserve space however. Besides, space is cheap. Sorry for watering your lawn, but it was kind of dry.
In this case, you should have you dev environment setup in a container (or VM) with the correct dependencies
Something that I have ran into is the mono runtime for gaming, it has many complicated dependinces which can easily conflict with the main system. I just ended up making full containers for older mono versions to get old games to work anyways.
Lol the conflicting the dependencies is a fantastic use for them, I just haven’t really run into that from a user perspective