Ryan Schmidt wrote: > > On Dec 11, 2008, at 14:42, Bryan Blackburn wrote: > >> On Thu, Dec 11, 2008 at 05:01:51AM -0600, Ryan Schmidt said: >> >>> I don't know what anyone else's thoughts were about how long we >>> wanted to >>> let 1.7.0-rc1 simmer before releasing 1.7.0 final, but I would like >>> to not >>> release 1.7.0 until this regression I just found is fixed: >>> >>> http://trac.macports.org/ticket/17610 >> >> Since the -sdk option is present in the Xcode group, this doesn't need to >> affect 1.7.0 at all, as the group code is in dports/ [1] and can be fixed >> whenever. >> >> Bryan >> >> [1] - >> <http://trac.macports.org/browser/trunk/dports/_resources/port1.0/group/xcode-1.0.tcl> >> > > It's true that the xcode portgroup file has moved to the dports > directory and that therefore we can fix this issue without needing a new > MacPorts release. However, MacPorts 1.6.0 does not use the xcode > portgroup file in the dports directory; it uses a different copy of that > file which predates this change. So MacPorts 1.6.0 users can currently > install xcode-portgroup ports with the universal variant (if the > individual ports support it). Some ports like sleepwatcher presently > even require the universal variant. If we release MacPorts 1.7.0 without > having fixed this issue, Tiger users will no longer be able to install > xcode-portgroup ports with the universal variant. So that is a > regression I'd rather not have.
I'd debate this some more, but I figured this would be faster: "Fixed in r43621." ;-) - Josh _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
