[macports-ports] branch master updated: gnuradio*: rev-bump for updated Jack ABI.

[Michael Dickens]

If you use otool for the self-id on the resulting libraries you'll see that the old jack ("0.124.1_2") produced:
{{{
        /opt/local/lib/libjack.0.dylib (compatibility version 1.0.0, current version 1.28.0)
}}}
while the new one ("1.9.12_0") shows:
{{{
        /opt/local/lib/libjack.0.dylib (compatibility version 0.0.0, current version 0.1.0)
}}}
So either the ABI has changed or the "new" jack's library version creation settings are incorrect. Either way, a rev-bump fixes the issue & makes "port rev-upgrade" happy too ;) I do think that the Jack API and ABI are actually upgrade-compatible beyond the internal versioning issue listed here. - MLD

On Fri, Apr 6, 2018, at 8:13 AM, Ryan Schmidt wrote:
> 
> On Apr 6, 2018, at 06:49, Michael Dickens wrote:
> 
> > Michael Dickens (michaelld) pushed a commit to branch master
> > in repository macports-ports.
> > 
> > 
> > https://github.com/macports/macports-ports/commit/398bdaad2d3e7c6f0af1cf92658f6d06f9e33971
> > 
> > The following commit(s) were added to refs/heads/master by this push:
> > 
> >      new 398bdaa  gnuradio*: rev-bump for updated Jack ABI.
> > 
> > 398bdaa is described below
> > 
> > 
> > commit 398bdaad2d3e7c6f0af1cf92658f6d06f9e33971
> > 
> > Author: Michael Dickens
> > AuthorDate: Fri Apr 6 07:49:32 2018 -0400
> > 
> > 
> >     gnuradio*: rev-bump for updated Jack ABI.
> 
> Did you notice a problem before this rebuild? The new Jack was thought 
> to be compatible with the old Jack, which is why revbumps weren't done. 
> If that's not so, then we may need to revbump anything else that links 
> with Jack.
>