Sure, I'm interested in any improvement that is for the greater good of the community. I don't know much about Linux distributions so I wouldn't know how to set up the make files correctly.
If the library version should be included in the shared file name, then that has to be done automatically by reading the version from the angelscript.h file. I do not want to have to remember updating version numbers in multiple different files for every new release. I'm already having difficulty remembering to update the version number in the manual .
All 3 numbers would have to be included in the file name. The first number (2.x.x) is the script language version. This will change when I implement something that completely breaks backwards compatibility with previous scripts. The second number (2.29.x) is C++ interface version, this changes everytime I make any change to the interface that may require a modification in the application code. The 3rd number (2.29.2) is the closest thing to the ABI version, I change this number whenever I implement new features but do not change the C++ interface. The application has to be recompiled whenever a new version is used, but it shouldn't be necessary to modify any code if only the last number is changed. When I'm only making bug fixes to an existing library I add a letter to the version string, e.g. 2.24.0a, 2.5.0c, etc.
I don't know anything about any existing FindLibAngelScript. How would it work?