Allowing more non-maintainer updates

[Jeremy Lavergne]

I like the idea.

How about we add removing changes that were rolled back previously  
that were accidentally/blindly reinstated?
adding comments?

We might consider expanding the "hardcoded" section to include other  
items, such as moving ports off of about-to-be abandoned packages  
(e.g., python24) or changes to base (e.g., `default parallel_build  
yes`).  We might also consider upgrading PortGroups, if that day ever  
comes to pass.

On Jul 22, 2009, at 4:57 PM, Ryan Schmidt wrote:

> The Non-Maintainer Port Updates section of the guide lists  
> conditions when we may update ports that have a maintainer:
>
> http://guide.macports.org/#project.update-policies.nonmaintainer
>
> The existing conditions are:
>
> * The maintainer does not respond within 72 hours
> * A port is abandoned by its current maintainer
> * A critical port is broken that affects many users
>
> There are some conditions I would like to add to these:
>
> * Required port variable missing (e.g. platforms or long_description)
> * Syntax error
> * Spelling or grammar error in comments, descriptions, etc.
> * Hardcoded /opt/local
> * Forgot to bump revision or epoch after change that requires it
> * No $Id$ tag
> * No svn:keywords or svn:eol-style properties
> * Build fix for pre-release Mac OS X version
> * Removing code for very old versions of Mac OS X (I would currently  
> limit this to Jaguar and earlier; once MacPorts 1.8.0 is released,  
> make this Panther and earlier)
> * Removing code for ports which will be deleted (e.g. removing  
> mysql3 variants since I want to remove mysql3 port)
>
> Thoughts? Additions?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2435 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20090722/5af894fe/attachment.bin>