"Better" doesn't come from "simpler". Your solution won't track Steam updates, because it's a one-off copy, instead of linking to the original file that's being kept up-to-date. It'll become obsolete with the first Steam update. So I'd say it's clearly an inferior one. I could give you a oneliner command if that makes you feel betteromano;n2331770 said:What I mean is that I just overwritten the file ~/Steam/KF2Server/Binaries/Win64/lib64/steamclient.so with the file ~/Steam/KF2Server/linux64/steamclient.so of my installation, and it worked so I don't know which is best. Mine seems less files modified so I would say is better
In any case, there's no "good" solution we users can provide, since this will all break again with the very first integrity check, since the KF2 package contains checksums for the original (wrong) files. I'll modify killinuxfloor to enforce the symlinks with every (re)start, that's all I can do. So an integrity check will put the old wrong files back in place, then the starter script will remove them again and add links to Steam's .so again. Sounds stupid, doesn't it?
The actual solution to the problem would be Tripwire removing the bundled steamclient.so files (and I mean all of them) and relying exclusively on Steam's version. Bundling 3rd party libraries is a horrible practice, particularly so (pun intended) on Linux, and this has been common knowledge since the 90s. I could go on technicalities, but I'd rather not bore you with them, our current issue is a perfect demonstration on its own.