Currently, SIPEAdiumPlugin comes explicitly linked to version 2.10.5r590f15aee045 of libpurple, 2.32.4 of libglib and 0.18.1.1 of libintl:
$ otool -L SIPEAdiumPlugin.AdiumLibpurplePlugin/Contents/MacOS/SIPEAdiumPlugin SIPEAdiumPlugin.AdiumLibpurplePlugin/Contents/MacOS/SIPEAdiumPlugin: ... @executable_path/../Frameworks/libpurple.framework/Versions/2.10.5r590f15aee045/libpurple (compatibility version 11.0.0, current version 11.5.0) @executable_path/../Frameworks/libglib.framework/Versions/2.32.4/libglib (compatibility version 3201.0.0, current version 3201.4.0) @executable_path/../Frameworks/libintl.framework/Versions/0.18.1.1/libintl (compatibility version 10.0.0, current version 10.1.0)
Many Adium updates update libpurple for security issues and bugfixes, this makes the plugin not load anymore, leading to rather... impolite feedback like https://trac.adium.im/ticket/16363.
However, the libpurple API/ABI guidelines guarantee that a plugin linked to libpurple 2.x.y will continue to work for all newer 2.z.w releases.
So you could avoid this problem by linking to the newest version, every framework has a
Versions/Current alias pointing to the latest version it includes, using for instance
If you're too concerned about updates that break the plugin, we (the Adium team), could start adding intermediate version aliasses, like
Please let me know what you think about this!