[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Interface range compatibility?
From: |
Phillip Susi |
Subject: |
Interface range compatibility? |
Date: |
Wed, 02 Oct 2013 11:30:20 -0400 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 |
-----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 app against this
library, I would expect it to prefer interface 1 and there to be a
libfoo.so.1.0.0 symlink it would request, but there isn't. Therefore,
when I decide to drop support for the old interface 0 from the library
by dropping the age to 0, the app no longer can find the library,
which is now libfoo.so.1.0.0.
What am I missing here? How do you get the app to prefer the newer
interface ( and thus, work when the old interface is dropped ) while
allowing older apps to use the old interface for a while?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSTDwMAAoJEJrBOlT6nu75RqgIAIiw/g03kXDUoHXreuT1Prwl
DM2p/D7ffHm2Gb5AMZw38mL50MKkVxjk2C4R+uOHmdFxl0LYvM9Pt7rhuTQPoZGq
jVEzwnzl7ltEfVYogj7lrvuG9Y5DjmQLrjcomUpXeSkBr/snoygXkG9xNwWu2g7U
PYwXt/yjZeng9N1adBobSzDIXQnE9qOxpZ1J5IHQo2GOTQxHHAA30AY90r9rGRmO
KxLwexjFSCoB9DL0yHxPm6iLmzuCi0doAC6NhdVJd5Kliv/aTayCX+s+gfC3ZBh/
84P72RMHmSHVp+f2hc3Q3Al2HpbqR4FfFTXi5sF8Db6MTwR26aFBztzJwM9B5K0=
=Jug9
-----END PGP SIGNATURE-----
- Interface range compatibility?,
Phillip Susi <=