Jeremy Huddleston Sequoia
jeremyhu at macports.org
Sun Apr 13 19:22:39 PDT 2014
On Apr 13, 2014, at 16:51, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Apr 13, 2014, at 10:57, MK-MacPorts at techno.ms wrote:
>> Yesterday I noticed - while installing a MacPorts from scratch - that after all the port tiff got rebuild by rev-upgrade.
>> Looks like tiff would need a revbump right?
>> How is the policy regarding such cases??
>> Shall one simply commit a revbump whenever one spots a port like that
>> do we rely fully on rev-upgrade doing its job?
> If a binary on our packages server is mislinked (i.e. linked with a previous version of a dependency’s library) such that rev-upgrade decides to rebuild it, we should revbump to fix the binary package.
> However, I looked at one of the binary packages (tiff-4.0.3_2.darwin_10.x86_64.tbz2) and did not see any obvious mislinking. Do you know why rev-upgrade decided to rebuild tiff on your system?
> We do need to revbump tiff anyway in the process of fixing this issue:
> Jeremy, the last note in the ticket from awhile ago said you were looking into it?
Yeah, I never really got around to tackling that. It's not broken, just slow (using muniversal for now).
More information about the macports-dev