Lawrence, The only part of the guide which could be used as an excuse for committing that change would be "A critical port is broken that affects many users".
Of the ports listed by running 'port echo depends:webkit-gtk' the only big deal I could see was gimp2. The only users who would have been left in limbo would be those installing webkit-gtk dependents for the first time after r96828. Ticket #35737 could have sat for longer than 19 hours while the maintainer, who chose to take exclusive control of webkit-gtk, may have been able to begin researching (or letting users submit) an appropriate solution. The fix which was committed well before the 72 hour maintainer timeout period seems to have been the wrong solution for the problem. Perhaps a patch could be added to the ticket and a request sent to macports-dev and/or portmgr for permission before jumping to the conclusion that "A critical port is broken that affects many users." Ryan Stonecipher On Sun, Aug 19, 2012 at 3:01 PM, Lawrence Velázquez <[email protected]> wrote: > On Aug 19, 2012, at 2:04 p.m., Ryan Stonecipher wrote: > >> When a port has a single maintainer, when is it acceptable to commit a >> quick/obvious change to fix a bug? > > http://guide.macports.org/#project.update-policies > > vq > _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
