On 11/10/11 11:48 AM, Brian White wrote: > Thanks for all of the quick responses. I didn't realize /usr/local > would cause a problem (obviously since I usually try to avoid shooting > myself in the foot right away :-) so per your recommendation I will > choose option 1. > > Thanks again! > Brian >
Yeah. The problem is that it's "special" on OS X, and the build tools are hardcoded to look there, even in the absence of explicit compiler flags. That, and a lot of third-party distributors of packages have them install there, because it's the default location. Problems come in when: 1) A third-party library doesn't match up with the corresponding Fink library for some reason (different version, different architecture, different options, etc.) 2) A user decides to clean out libs in /usr/local and unwittingly breaks their Fink installation. Hence the checks by the "fink-package-precedence" script. We encourage people not to install at the top level of /usr/local for yet another reason: 3) An incompatible third-party library, etc (as per 1) can overwrite Fink's version of the library and break stuff. It may be the case that /usr/local/<somesubdirectory> is no more dangerous than is /sw (I'm not at all sure about this), but the 'fink-package-precedence' script, which is in fairly widespread use, isn't set up to cope with that. -- Alexander Hansen, Ph.D. Fink User Liaison http://finkakh.wordpress.com/ ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Fink-users mailing list [email protected] List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
