Bryan Blackburn wrote: > On Fri, Mar 06, 2009 at 04:37:01PM -0500, Orville Bennett said: >> On Mar 6, 2009, at 11:52 AM, Ryan Schmidt wrote: >>> On Mar 5, 2009, at 09:24, [email protected] wrote: >>> >>>> Revision: 47756 >>>> http://trac.macports.org/changeset/47756 >>>> Author: [email protected] >>>> Date: 2009-03-05 07:24:46 -0800 (Thu, 05 Mar 2009) >>>> Log Message: >>>> ----------- >>>> upgrade: split upgrading dependencies into a separate proc, and use >>>> it to make sure that before new ports are installed during upgrade, >>>> their dependencies are upgraded. >>> Now that's just fantastic! Thanks. >> I'm a bit more apprehensive about the awesomeness of this. >> Is there some check which ensures that upgrading the dependency doesn't >> break the app that's updated? >> I already know the answer is no and that this is unlikely to happen. For >> those of us using macports for packaging though, a switch to turn this off >> would be welcome (please). Preferably in macports.conf >> "recursive_upgrade true/false" sounds nice :-) > > 'man port' mentions -n, which should still work here, otherwise I'd call > that a bug. > > Bryan
The new code can't be reached if -n used, so there's no need to check for it there. This did make me realise, though, that -R was not being handled correctly in the new code. Fixed now. :-) - Josh _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
