On Tue, Aug 27, 2013 at 12:18 AM, Lawrence Velázquez wrote: > On Aug 24, 2013, at 7:29 AM, Mojca Miklavec wrote: > >> - Should this be addressed in a single commit or should ports be >> changed one-by-one? (If one-by-one, some ports will be non-functional >> for the time of updating.) > > It's fine to do a single huge commit if all the changes are to fix exactly > the same issue.
If the current port is several years old and doesn't support wxWidgets 2.9, it's almost a phylsophical question whether or not upgrading it also fixes the same issue (making it compatible with 2.9) or not ;) > Don't throw in version updates and maintainer changes. In that case I need to choose either: (A) (i) upgrade all ports to the latest version and make them work with wxWidgets30 (ii) upgrade wxWidgets core ports (iii) revbump all ports updated in (i) or (B) (i) upgrade wxWidgets core ports and leave dependencies in a broken state for a few minutes (ii) upgrade dependencies one by one The drawbacks of (A) are: - a lot of extra work - all ports will need revision >= 1 at the end I don't think that anyone would really be affected by a small time lag in (B), so if updates need to be separate, I would prefer to choose (B). Mojca _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
