New Mac, should I use Macports?

Question

got a new Mac, you need to configure it for development. I heard about macro ports, can I use it? Is it really easier than manually downloading and compiling? who has problems using it?

This is a typical material for creating a ruby ​​website.

thanks

Answer 1

Try homebrew . This is really good because it is highly optimized and has no redundant packages.

It is also built in Ruby , which seems especially relevant to you.

Answer 2

This is easier than doing it manually. For instance:

  sudo port install gimp

download, build and install Gimp, as well as all its dependencies. There are many dependencies.

If you are doing “typical” things, there will be enough versions of things in MacPorts. Only if you need to be on the verge of bleeding, you need to get around MacPorts and download and install manually.

Answer 3

While macports simplifies installation, this is the difference between the 4 commands (wget / tar / configure / make) and command 1. Where the macros really glow, this is package management. If you are primarily interested in developing Ruby, RubyGems may be all you need. If you are doing Ruby on Rails, macports will be very useful for all the ruby ​​software you need. If you want to make full use of the GUI, you can use Porticus as the macports interface.

I had a random problem during the build phase, but this is under the tiger, which is behind the times.

Answer 4

I prefer macports, but some like to do it on their own. Macports generally lags behind releases, but it's still good for me.

Answer 5

The biggest problem with macports is that it does not cross the platform, and it is difficult to define a well-defined development scenario (for example, you are using Foo version 1.2.3, Bar version 0.5.6, etc.). It simplifies your life, but to date, I still have not found a decent solution for defining and creating a development environment that is efficient, simple and cross-platform. See also this question .

So my suggestion is to go with macports if you don’t want to very strictly control the development environment.

Answer 6

You should use the package manager if you do not have a clearly defined, specific reason.

'Of course I prefer fink .