% otool -L /opt/local/lib/libQtCore.4.7.4.dylib
/opt/local/lib/libQtCore.4.7.4.dylib:
/opt/local/lib/libQtCore.4.dylib (compatibility version 4.7.0, current
version 4.7.4)
No rev bumps required until qt5. (Unless they've seriously messed up
their library versioning, which I doubt.)
- Josh
On 2012-4-13 23:46 , Michael Dickens wrote:
> Actually, the primary installed library names are changing (from,
> e.g., libQtCore.4.7.4.dylib to libQtCore.4.8.1.dylib) and then the rest
> are just soft links to this file. Hence, depending on how the dependent
> project is linked, it may or not require a rev bump. So, doing the
> revupgrade_mode seems like it would be wise, and I'll do so once I get
> to that point; hopefully later today, but we'll see. I remember the last
> time there was a major update to Qt, and the revision changes were quite
> the PITA; we do what we have to do :) - MLD
>
> On Apr 13, 2012, at 9:40 AM, Joshua Root wrote:
>> If the linking will be broken, revisions still need to be incremented.
>> You can use rev-upgrade to help with this: setting 'revupgrade_mode
>> report' in macports.conf will make it show you all the installed ports
>> that are broken but not rebuild them. (I'd recommend this mode for
>> developers so you're prompted to rev bump ports that need it.)
>>
>> However, it doesn't look like the soname is changing, so are you certain
>> that rebuilding is necessary?
>>
>> - Josh
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
