On May 31, 2013, at 14:02, Clemens Lang wrote: > On Fri, May 31, 2013 at 11:21:24AM -0500, Ryan Schmidt wrote: >> I had kind of hoped we weren't going to update icu until after >> MacPorts 2.2 had been released because of the library overlinking >> issue and all of the revision increases this necessitates. >> https://lists.macosforge.org/pipermail/macports-dev/2013-February/021943.html > > We should get this change out of the door sooner than later, yes. > Regarding the ICU update, there's not much we can do now – the damage is > done, the rev-bumps will have to trickle in now anyway.
Agreed. And thanks for doing a lot of the work already. > Avoiding updates because of the necessary revbumps sounds like a broken > concept to me, though. For the same reasons we could stop updating > libpng or openjpeg. Indeed I am delaying updating libpng to 1.6.x for this reason. > If revbumps are such a hassle, we should try > automating them as much as possible, e.g. but keeping track of the > linking or modifying rev-upgrade in a way that will do them as quickly > and easily as possible. > > If you want this change out there, push 2.2 or backport the change and > release 2.1.4, but delaying updates until an unknown future date doesn't > sound like a good idea to me. I agree we should release MacPorts 2.2 ASAP for this reason. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
