In my particular case the problem was caused by having installed
MacPorts on a PPC based system, using Migration Assistant to move
things over to an Intel based system and THEN trying to run
selfupdate. Not a real common set of circumstances and one that was
pretty easily solved (and one I think most MacPorts users would be
able to figure out on their own).
-Stuart
On Nov 16, 2007, at 2:22 PM, Daniel J. Luke wrote:
On Nov 16, 2007, at 2:14 PM, [EMAIL PROTECTED] wrote:
On the other hand, if a user installs stuff in /usr/local/ after
installing MacPorts it wouldn't help unless selfupdate (and/or
port) also
checked those paths so maybe it isn't feasible. The Cisco VPN
client uses
/usr/local, though it causes no problems. Comments?
So the 'problem' is only when the user installs some library in /usr/
local that macports uses and either that install is broken somehow
or the user removes it.
It's good to make macports robust against mistakes, but at some
point we probably have to realize that end-users are going to be
able to configure their systems in ways that are broken, and we may
or may not be able to do something about that specific broken-ness.
--
Daniel J. Luke
+========================================================+
| *---------------- [EMAIL PROTECTED] ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
| Opinions expressed are mine and do not necessarily |
| reflect the opinions of my employer. |
+========================================================+
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
--------------------------------------
Stuart Tannehill
[EMAIL PROTECTED]
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
