-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/4/2013 5:39 AM, Peter Rosin wrote:
> The libfoo.so.1.0.0 symlink isn't there because it will never be
> used, at least not if you follow the rules. It is not allowed to
> simply reset age to zero. You have to also bump interface in that
> case.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If I fix a bug in a library and bump the revision level ( and not the
interface ), then an executable linked to the library will be able to
use either version at runtime. Is there a way for the executable to
figure out which version it is using at run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If I build rev 0 of a library, link to it, then rebuild the library
with interface 1, age 1, that should mean it is compatible with
interface 0 or 1. It creates libfoo.so.0.1.0 so an app linked against
interface 0 will find it. Now if I rebuild the a
