Marcus Bointon wrote:
I don't see why it should be looking in the current dir to upgrade outdated packages anyway, and it's obviously not having any trouble finding the portfiles in the normal install location. Is it that 'outdated' resolves to ''?
Just sounds like a bug in MacPorts 1.6.0... http://trac.macports.org/ticket/12288 --anders _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
