Dependency hell happens when you try to go against your distro and install something. Someone who used Linux for 20 years probably found a distro that works well for them, hence the no dependency hell.
Or they just stopped tinkering. Either case is solvable by Nix/Flatpak/Bedrock/20+ other solutions
I had one 4 months ago when installing an industry-standard SEO tool on Ubuntu. It was severe enough Ubuntu borked it’s own GUI. Though to be clear, my comment wasn’t saying I get one everyday - I was saying I would make the same choice if asked everyday. English is not my native language.
It’s common on Ubuntu/Debian. They’re stable releases, plus there are repos for them all over the place. This unfortunatelly leads to dependency hell, sooner or later. If you use only the provided repos, that will most likely never happen.
If I use the provided repos, the software is no longer compatible - the .deb conflicts with the packages in the main repos.
Compare it to Windows, where I don’t need to explain to my boss why installing a tool everyone uses made me have to go away for 2 hours. I just download the .exe and I don’t ever care about a “DLL conflict” from any repos whatsoever.
In over 5 years? Like when containers and flatpaks became popular and include all their dependencies? Or when RHEL8 introduced app streams to help combat dependency issues?
I’m genuinely curious too. Was there a big update? Bad interaction with the new plasma? I know they added av1 last year but I looked like a week ago and atsc 3.0 and ac4 audio still didn’t work.
I mean luckily distro maintainers usually deal with it (quite a lot of work) but have any additional repos and it gets wonky if those are not in total lockstep.
Yeah, that is true as well. I meant Debian/Ubuntu because it has the most 3rd party repos available. But yes, if you have more than one package manager, then things will most likely go south after a while as well.
Well not two different package managers but just two repos from different people (so hard to keep deps in sync). Packman (the third party codec repo for openSUSE) is slower to update compared to official repos, which often results in a situation where a thing from Packman requires a different version of a library than stuff from official openSUSE repos. But in that case it is easy to solve (for the user) in that you’ll just have to wait a bit for Packman people to figure out the situation.
Damn near 25 year Linux user here, servers, desktops, everything. I haven’t seen a single dependency issue in over 5 years.
ಠ_ಠ
Yeah, to be honest, they’re less and less common, especially with rolling release distros.
So lucky ones do exist after all
I get what you mean, but the way you worded it makes it seem like you experienced dependency hell for 20 out of 25 years…
Dependency hell happens when you try to go against your distro and install something. Someone who used Linux for 20 years probably found a distro that works well for them, hence the no dependency hell.
Or they just stopped tinkering. Either case is solvable by Nix/Flatpak/Bedrock/20+ other solutions
Quick question can you suggest some lotto numbers thx
I had one 4 months ago when installing an industry-standard SEO tool on Ubuntu. It was severe enough Ubuntu borked it’s own GUI. Though to be clear, my comment wasn’t saying I get one everyday - I was saying I would make the same choice if asked everyday. English is not my native language.
It’s common on Ubuntu/Debian. They’re stable releases, plus there are repos for them all over the place. This unfortunatelly leads to dependency hell, sooner or later. If you use only the provided repos, that will most likely never happen.
If I use the provided repos, the software is no longer compatible - the .deb conflicts with the packages in the main repos.
Compare it to Windows, where I don’t need to explain to my boss why installing a tool everyone uses made me have to go away for 2 hours. I just download the .exe and I don’t ever care about a “DLL conflict” from any repos whatsoever.
In over 5 years? Like when containers and flatpaks became popular and include all their dependencies? Or when RHEL8 introduced app streams to help combat dependency issues?
ffmpeg was like three weeks ago
What happened with ffmpeg ?
I’m genuinely curious too. Was there a big update? Bad interaction with the new plasma? I know they added av1 last year but I looked like a week ago and atsc 3.0 and ac4 audio still didn’t work.
Did that cause breaks on certain distros? No issues with it on Arch.
I mean luckily distro maintainers usually deal with it (quite a lot of work) but have any additional repos and it gets wonky if those are not in total lockstep.
That’s a Debian/Ubuntu specific issue. Repos all over the place, so yeah, you will break things eventually.
No it isn’t, any distro might have these issues if they have third party repos. openSUSE commonly has these conflicts with Packman.
Yeah, that is true as well. I meant Debian/Ubuntu because it has the most 3rd party repos available. But yes, if you have more than one package manager, then things will most likely go south after a while as well.
Well not two different package managers but just two repos from different people (so hard to keep deps in sync). Packman (the third party codec repo for openSUSE) is slower to update compared to official repos, which often results in a situation where a thing from Packman requires a different version of a library than stuff from official openSUSE repos. But in that case it is easy to solve (for the user) in that you’ll just have to wait a bit for Packman people to figure out the situation.
Oh, packman, I misread pacman 😁.