|
|
|
|
|
by mehrdadn
3077 days ago
|
|
> I'm guessing you don't know what "DLL hell" was. I do. And like you said: "was". That's why I asked which version of Windows parent is talking abomut. Why are you bringing it up so many years later when you explicitly acknowledge it "was" rather than "is"? > Don't blame the tool if you don't know how to use it properly So many of you are baselessly claiming this yet none of you are telling me what I could have possibly done "improperly" to get into this mess. I told it to update everything. And there were no packages that had more updates... except these ones which wouldn't budge. If just telling my system to update and letting it do whatever it wants is "not using it properly" then -- to put it as nicely as I can put it -- there is a UI/UX problem. (Read: it would do a good job of explaining why a Linux distro isn't the main desktop OS, wouldn't it.) |
|
The reason you're getting so much push-back on this issue, I feel, is that there are far, far more benefits to package management than disadvantages, and in your special case you managed to get into a state that led you to the wrong conclusion, alas. Your package manager was protecting your system, as it is designed to do - what you needed to do was identify which package had the foul dependencies, and either decide to override the package manager, or uninstall the original app - which I believe was Steam.
Steam on Linux does have gotcha's - one of which, the designers of Steam also don't want to have to maintain a package repo or play nice with distro's efforts to keep peoples systems clean and well-maintained (too expensive to actually play along) .. so the fact that you were being tripped up by Steam, and subsequently blamed Linux-worlds' package management, is double-frustrating for those of us who have been using package management for decades and consider it one of the principle advantages to being Linux users, over the hell of Windows installation that has cropped the industry for decades.