3 ms·
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
by ROFISH 18y ago
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.
- Zev 18y agoThats 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.
- reconbot 18y agoWhat 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.
- Zev 18y agoInconsistent library versions when compiling programs. Hacks that can break very easily to detect system libraries.
- sho 18y agoHow 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 ...