List:MySQL++« Previous MessageNext Message »
From:Warren Young Date:May 19 2010 9:14pm
Subject:Re: v3.1.0 imminent
View as plain text  
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.
Thread
v3.1.0 imminentWarren Young13 May
  • Re: v3.1.0 imminentRick Gutleber14 May
    • Re: v3.1.0 imminentWarren Young14 May
      • Re: v3.1.0 imminentRick Gutleber14 May
  • Re: v3.1.0 imminentRemi Collet19 May
    • Re: v3.1.0 imminentWarren Young19 May
      • Re: v3.1.0 imminentWarren Young19 May
        • Re: v3.1.0 imminentJonathan Wakely20 May
      • Re: v3.1.0 imminentRemi Collet20 Jun
        • Re: v3.1.0 imminentJonathan Wakely20 Jun
          • Re: v3.1.0 imminentWarren Young21 Jun
            • Re: v3.1.0 imminentRemi Collet21 Jun