[47756] trunk/base/src/macports1.0/macports.tcl

[Orville Bennett]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Mar 6, 2009, at 11:52 AM, Ryan Schmidt wrote:

>
> On Mar 5, 2009, at 09:24, jmr at macports.org wrote:
>
>> Revision: 47756
>>          http://trac.macports.org/changeset/47756
>> Author:   jmr at macports.org
>> 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 :-)

> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkmxl30ACgkQ2yWVgjgEOKT71QCeIpnXhn2WHAoEIA0Q7AvWhEm7
3MkAnR1jl1euo6b60jmJemJtIXJoeEM7
=qHOB
-----END PGP SIGNATURE-----