Admittedly, I have not taken the time to try MacPorts specifically. (This is probably due to the fact that the lab machine I worked on was polluted by various things installed via MacPorts, which seemed to mess with the autotools/configure process even further, if I was trying to compile something in ~/src. Left a bad taste in my mouth. But that's obviously not MacPorts' fault.)
My experience is that these third-party package managers are great, until you want to make them work with software that doesn't come through the package system. A good test case, I think, would be this: how easy is it to install Python via [MacPorts|Fink|Homebrew|etc.] and then compile and run the latest SciPy (say, a bleeding-edge version from source control, not one from the package manager) against that Python?
Can you speak to a case like this, or one of similar complexity?
Generally, it just means that you need to get your prefix set up right.
I've used MacPorts to install one dependency for something I was compiling by hand, and so I sort of did the opposite: I told MacPorts to install that particular package into the directory where I had hand-built the rest of them.
My experience is that these third-party package managers are great, until you want to make them work with software that doesn't come through the package system. A good test case, I think, would be this: how easy is it to install Python via [MacPorts|Fink|Homebrew|etc.] and then compile and run the latest SciPy (say, a bleeding-edge version from source control, not one from the package manager) against that Python?
Can you speak to a case like this, or one of similar complexity?