On 04/01/2012 04:01 AM, Ryan Schmidt wrote: > To those who have worked on base: > > There are several little fixes merged into the 2.0 branch already > (and a few more I could merge) that could be released as 2.0.5, but I > see a 2.1.0 milestone was also created in Trac and several tickets > were assigned to it. I haven't been building from trunk so I don't > know what all's in there or if it's ready to go out. Should we > release 2.1.0 soon, or do a 2.0.5 release first?
rev-upgrade could still be improved to get faster in the step scanning for binary files. It currently does lot of I/O walking through files although this could be done in the activation phase where we know which files are being installed. However, such improvements could also be moved to 2.2.0 to avoid any delays for 2.1.0. I think the speed of the post-install/post-upgrade is good enough for now. Rainer _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
