Policy on upgrading dependents

Blair Zajac blair at orcaware.com
Sat May 21 19:21:49 PDT 2011

On May 21, 2011, at 6:39 PM, Clemens Lang <cal at macports.org> wrote:

> Hi,
> On Sat, May 21, 2011 at 06:37:04PM -0500, Ryan Schmidt wrote:
>>> Since we have a GSoC project to remedy this (correct me if i'm
>>> wrong) then YES, for the time being let's making your responsibility
>>> since it's very temporary.
>> It appears I need to acquaint myself better with what's going on with
>> GSoC!
> You're right, it is my GSoC project to find and rebuild such broken
> packages using a command named port rev-upgrade. If I can get it to work
> fast enough, we might be running it automatically after each upgrade,
> essentially fixing these revbumps once and for all.

It's not that simple if the new version is not source compatible.  I think it's incumbent on the committer to check that dependant ports do compile and provide any necessary patches for those ports to compile.


More information about the macports-dev mailing list