Hacker News Reader

Comment by ROFISH | Hacker News Reader

Personally, I've had more trouble with macports than necessary. (Mostly because whenever I type 'port', I still get command not found.) It's much easier just to download the source, ./configure, make, and sudo make install.

View on HN

Thats because macports installs itself to /opt/* which isn't in your $PATH. Easy to fix. But macports still causes more problems then its worth. So does fink for that matter.

What problems? Package dependency problems? The worse that I've had happen is having to deal with broken packages. The amount of times I haven't had to deal with figuring out dependencies makes it more then worthwhile, IMHO.

Inconsistent library versions when compiling programs. Hacks that can break very easily to detect system libraries.

How can you know how to do custom builds and not know how to fix your $PATH? ;)

  $ mate ~/.profile
  # add "/opt/local/bin:/opt/local/sbin:" to beginning of "export PATH"
  save

Now force a reload (eg. open a new terminal) and done ...

Reply on news.ycombinator.com