Bas, I'm not sure how to understand this. > So you go from (8.2.1): > > /usr/lib/x86_64-linux-gnu/libproj.so -> libproj.so.22.2.1 > /usr/lib/x86_64-linux-gnu/libproj.so.22 -> libproj.so.22.2.1 > /usr/lib/x86_64-linux-gnu/libproj.so.22.2.1 > > To (9.0.0): > > /usr/lib/x86_64-linux-gnu/libproj.so -> libproj.so.9.0.0 > /usr/lib/x86_64-linux-gnu/libproj.so.25 -> libproj.so.9.0.0 > /usr/lib/x86_64-linux-gnu/libproj.so.9.0.0 >
Are you suggesting that we ONLY use the major, minor and patch version numbers for the so-files and forget about the SOVERSION from now on? If that is the case, personally I'm all for it since I've always found the current/revision/age difficult (as is evident in several release candidates in the past) but is that a common practice among project that base their packages on CMake? /Kristian _______________________________________________ PROJ mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/proj
