From: Warren Young
Date: May 19 2010 9:14pm
Subject: Re: v3.1.0 imminent
List-Archive: http://lists.mysql.com/plusplus/8957
Message-Id: <4BF454C1.70807@etr-usa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 5/19/2010 10:49 AM, Warren Young wrote:
>
> Maybe one could be lashed up with nm?
I took a stab at this, and the results are almost unreadable, even to
me, and I know the details of everything that changed in this release.
nm tells you a lot of irrelevant stuff like object addresses, new
outside dependencies (e.g. getopt() and mysql_ssl_set() in 3.1), new
methods... None of that indicates ABI breakage.
What I want to know is if any method signatures changed, things like
that, but digging it out of the haystack of irrelevancy....rough.
>> are you going to bump soname ?
>
> I don't think so
I just checked it, and the main generated library is now called
libmysqlpp.so.3.1.0, but you also get a libmysqlpp.so.3 symlink, and
it's the latter that programs seem to link against, at least on my Linux
boxen.
I'd say if you can run existing binaries against a new 3.1 RPM, it's
probably safe to push it into a repository without warning anyone.