Hi, since I've done quite some base development since the last release I figured I'd chime in and offer my opinion.
Releasing the stdlib changes is certainly a good idea IMO. However, I'd argue we should drop the check currently present in rev-upgrade that will print warnings for ports built against a non-default stdlib – it generates a lot of warning noise for some ports, is not always easily fixable and useless for users. We should rather enable it on demand or move it to a different place (post-destroot perhaps?). A couple of stuff that could be done with new base, which I think is totally ready to be released ASAP: - curl post command and r116820 for package statistics. Some server-side and Portfile stuff still needs to be done for the statistics, but we'd have a base release ready for it. - Check for command line tools and Xcode license agreement. In r115900, we've seen a lot of reports of missing command line tools lately that could be solved by that. - Working trace mode. I've been building with trace mode enabled exclusively for the last 3 months and I'm pretty confident it's ready for a release. We could even modify FAQ#buildfails to suggest trying with trace mode on for all the people out there with a clobbered /usr/local. - r113704 fixing a regression quite a few people encountered with the sandboxing stuff. So, in general, I'd welcome a timely release of 2.3 :) I have the private copy of Tcl 8.5 coming up in the pipe and almost done, but if I'm not getting that done in on time it could wait for another release. -- Clemens Lang _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
