up vote 2 down vote favorite
share [g+] share [fb]

I'm having a problem of consistency between my machines because I have to explicitly specify the command path for some items like Image Magick. Port installs them to /opt/local/bin, but for consistency, I would like to install to /usr/local/bin. How can I specify that?

link|improve this question
Have you considered accepting an answer so the user receives points? – Nerdling Oct 1 '09 at 19:06
feedback

migrated from stackoverflow.com Sep 15 '09 at 22:03

This question came from our site for professional and enthusiast programmers.

3 Answers

up vote 7 down vote

Just add /opt/local/bin to your path, like the rest of us. You can do this in ~/.profile

Trying to force it to /usr/local/bin

  • is an unnecessary effort
  • risks executable or library collisions with evil and a potentially disastrous impact
link|improve this answer
Like I said originally though I have to explicitly specify the command path in the application code. We have more than one development machines so some have installed from source (/usr/local/bin) and some have installed from Mac Ports (/opt/local/bin). – Tom Sep 15 '09 at 19:09
2  
Either use MacPorts or don't: either way you should avoid using /usr – Nerdling Oct 1 '09 at 18:58
e.g. ln -s /opt/local/bin/convert /usr/local/bin/convert – fideli Dec 12 '09 at 4:07
feedback
up vote 5 down vote

Macports really does not like being in /usr/local. From MacPorts Faq

/opt/local was chosen so as to avoid stomping on other various installations (e.g. fink uses /sw to do the same); /usr/local is not a viable choice for several reasons:

  1. Some software (especially auto* tools from Gnu) look in /usr/local as a default location, which means MacPorts can't be easily isolated when needed
  2. /usr/local is usually reserved for the given system's admin to install items local to that system, and tends to be a bad choice to have taken over by a non-system port system
  3. gcc considers /usr/local to be a standard system directory, causing (at least) the include directory to be unable to appear early in the list of include directories, and hence causing MacPorts-installed items to be difficult to use properly for items which need them (where another version is installed elsewhere, like /usr/X11R6)

Also if you have installs from different sources are you sure that they are exactly the same version. If they are not then you will have odd build and runtime issues.

If after all that you still want to try to us this unsupported method and you just cannot use the path to find things I suspect it would be easier to make your code look in /opt/local/bin then /us/local/bin then choose the one it finds (also what happens if both are there)

link|improve this answer
feedback
up vote 0 down vote

If you know what you are doing, here is how to do it:

Installing Mac Ports from source.

link|improve this answer
1  
You should absolutely avoid using /usr as noted by Mark. – Nerdling Oct 1 '09 at 18:59
feedback

Your Answer

 
or
required, but never shown
discard