On Jan 4, 2010, at 17:23, Guilherme P. de Freitas wrote: >> Safest would be to rename /usr/local to something like >> /usr/local-disabled when building. Note that this applies to building >> ports as much as to selfupdate. Unfortunately this is necessary because >> of hardcoded behaviour in gcc that we can't work around. >> >> - Josh > > Ok, I have quite a lot of stuff (important stuff) in /usr/local, so I > want to make sure I won't mess this up. You are saying that before > installing, updating/upgrading anything with Macports I should run: > > $ mv /usr/local /usr/local-disabled
Yes. > And then after it is built, I can simply move back: > > $ mv /usr/local-disabled /usr/local If you must. :) Though it would be less error-prone in the long run to use MacPorts to install whatever software you require in /opt/local, and then remove /usr/local entirely. If you use software which does not exist in MacPorts yet, perhaps new ports can be created to fill those gaps. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
