E
Eric Ross
Guest
This may not be a new one, but here it goes..
Basically, 'force' any third party libraries such as libSDL to name a GENERIC .so library and keep the version numbers in comments in the library itself and NOT the name. In such a scenario, if I were to try to play a game looking for 'libSDL1.2' but the latest libSDL2.0 exists, this could be a replacement for asking the less contemporary user to create a symlink to it. I think it could reduce many issues with incompatibilities among distros. If there is a problem and the application or game is well written, it will bomb and log an error displaying 'newer library version required', 'library obsolete', '64bit version incompatible', or other message. My ultimate goal here is to be able to distribute or play binaries without running into dependency heck.
Does this make sense and could it be implemented? I've had to symlink a libray to a few games, X9 plane simulator comes to mind.
Thanks.
-ER
Basically, 'force' any third party libraries such as libSDL to name a GENERIC .so library and keep the version numbers in comments in the library itself and NOT the name. In such a scenario, if I were to try to play a game looking for 'libSDL1.2' but the latest libSDL2.0 exists, this could be a replacement for asking the less contemporary user to create a symlink to it. I think it could reduce many issues with incompatibilities among distros. If there is a problem and the application or game is well written, it will bomb and log an error displaying 'newer library version required', 'library obsolete', '64bit version incompatible', or other message. My ultimate goal here is to be able to distribute or play binaries without running into dependency heck.
Does this make sense and could it be implemented? I've had to symlink a libray to a few games, X9 plane simulator comes to mind.
Thanks.
-ER