Binary packages not rebuilding against updated libraries

[Perry E. Metzger]

On Thu, 26 Apr 2018 01:46:27 +1000 Joshua Root <jmr at macports.org>
wrote:
> On 2018-4-26 01:34 , Ryan Schmidt wrote:
> > 
> > On Apr 25, 2018, at 09:02, Perry E. Metzger wrote:  
> >> On Tue, 24 Apr 2018 09:31:04 -0700 Ken Cunningham wrote:  
> >>> Portfile authors need to manually "revbump" the library's
> >>> dependent ports when supporting libraries change significantly.
> >>>
> >>> It's not automatically figured out by MacPorts.  
> >>
> >> Do we have a Trac issue for having it automatically determined,
> >> btw?  
> > 
> > I doubt it, since I doubt there's anything we can do about it.
> > How would you automate that?  
> 
> It should be possible, but it would be some work. You'd have to
> install and run rev-upgrade on every dependent port each time any
> port is updated, and if it finds broken files and the rebuild
> succeeds in fixing them (i.e. a rev bump would fix the problem),
> you could commit a rev bump.
> 
> One complication is that we don't currently have a reliable way of
> programmatically rev bumping ports (it gets tricky when there are
> subports for one thing). Just notifying maintainers would still be
> a win though.

I don't know that this is needed. As I noted, there are other package
systems that just note that they have to rebuild dependents if a
package they depend on has a major version bump.

Or maybe I don't understand the problem well enough?

-- 
Perry E. Metzger		pmetzger at macports.org