“Use Fink until it pisses you off, then switch to DarwinPorts. That’s what everyone else seems to do.” : from jwz’s blog.
“Indeed”, he said, as he executed “sudo rm -rf /sw” on his developer machine at work.
(That’s not to say MacPorts is a utopia free from stupid issues though, it just seems to guarantee more consistency).
One of the things I’ve noticed is that most OSX hints for setting up anything in *nix-land tell you to add path statements just to ~/.bash_profile, usually assuming that you’re working on your own machine. But if you’re ssh’ing to another OSX(or -nix based) and set up the path in the same way, this will probably cause vlad(and capistrano, I guess) to fail with “command not found”, since they use a non-interactive shell to run commands. There are simple fixes: enable PermitUserEnvironment in your /etc/sshd_conf file. Which works, but 1: it’s a potential security hole(paranoia, a game we all can play!), and 2: it’s overkill, because having your path in ~/.bashrc is the proper way to do it, as pointed out here.
