Thread by @gravislizard

gonna shit on linux some more. installing programs is an unmitigated tire fire. no operating system past or present has ever fucked this up so bad

i installed current centos because i was told it's better than fedora. k. let's install teamviewer.

my process for installing teamviewer on fedora: download file. click file. done. it then didn't work because wayland, but it installed and ran

centos: download rpm, click it. plain dialog with "this file is not supported." that's it.
lol ok. the OS has been running for less than five minutes and has already catastrophically failed the sniff test. but whatever, i'm gonna wipe it anyway, let's dance

rpm -ivh filename.rpm
i get a list of dependencies that aren't satisfied. ok. so? satisfy them.
i google this and of course there's no info on how to do it, if rpm even can.

on debian (which i'm not using atm for other reasons i don't want to get into) if something says it needs libqt5webkit, the fix is "apt-get install libqt5webkit", almost every time. i already learned on fedora that all the rpms are named in pig latin

i COULD fuck around with yum trying to work out the package name. googling it is usually useless, of course, just scads of machine-generated pages that don't make the answer to the most obvious questions at all clear, if they have it at all. but also that's below my dignity.

in one of the random horseshit forum threads (a very normal place to find solutions to 'how do i install a program') that contains a half dozen absolutely ludicrous proposed solutions, I find "yum --nogpgcheck localinstall filename.rpm", which will resolve deps

i do so, and it installs a dozen libraries. i walk away and come back to a screenful of error messages (it can't just succintly give the error, that's too much effort, so I get the raw printf debug of the problem)
in short: it needs libqt5webkit and won't say why it can't get it

Now I'm on a web 1.0 rpm package explorer trying to find the name. I should point out that the teamviewer site EXPLICITLY calls out centos as supported.

every single step of this is unforgivably bad. why does this RPM, which both rpm and yum ACCEPT, simply say "unsupported file" when I try to open it with the package manager, the default association for rpm files?

this is of course what I expect from linux. None of the GUI tools work. They work just long enough to make you think they work, then the facade falls away. there's literally no excuse for the SAME PROGRAM that fedora uses, that worked, to just give a terse error and close.

as always, the clamor is "well you should have installed debian / ubuntu" and honestly? i didn't reserve the brain space to remember why debian was a trash fire last time i looked at it. i installed it two weeks ago on a machine at work and it was laughably broken

but hey, this is a waste of time aand I'm gonna put windows on this laptop after I give up on all this horseshit, so let's give it a spin