The shlibs file should read something like:
libunity-scopes 1.0 libunity-scopes1.0 (>= 1.0.x)
Where 1.0.x is the last release where new ABI was introduced (currently
it omits the version assertion on the end).
For mediascanner2, I am not generating the shlibs file from anything,
but instead manually update it. It's not perfect, but I'm not sure of a
better alternative yet.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1548718
Title:
Need to update micro version in shlibs file when symbols are added
Status in unity-scopes-api package in Ubuntu:
New
Bug description:
Currently, we are writing only major.minor into the shlibs file. But,
if we add a new symbol to the public API and only increment the micro
version, we really need to write the micro version as well.
Unfortunately, that's a manual process, so we need to remember. With
the next version of abigail, it might be possible to spit out some
big-time warning or some such when new symbols are added to the public
API. At least that would help to remind us.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1548718/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
