Shreevatsa R wrote:
> The proper solution is for MacPorts to figure out a way of preventing
> its ports from looking outside ${prefix} -- whether /usr/local or /usr
> or any directory at all.

Unless you have a patch ready that fixes the problem The Right Way, I
don't see how informing users of the problem is a bad thing.

- Josh
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Reply via email to