全新 Mac，我应该使用 Macports 吗？
拥有一台新 Mac，需要对其进行设置以准备开发。我听说 macports 很棒，我应该使用它吗？它真的比手动下载和编译更容易吗？有人使用它有任何问题吗？
它适用于典型的 Ruby Web 开发内容。
谢谢
got a new mac, need to have it setup ready for development. I heard great things about macports, should i use it? Is it really easier than manually download and compile? anyone has any problems using it?
It is for typical ruby web development stuff.
thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
尝试自制程序。它真的很好，因为它经过高度优化，并且没有多余的包。
它也是用 Ruby 构建的，这似乎与您特别相关。
Try homebrew. It's really good because it's highly optimized, and has no redundant packages.
It's also built in Ruby, which seems particularly relevant to you.
这确实比手动操作更容易。例如：
将下载、构建和安装 Gimp，以及其所有依赖项。有很多依赖项。
如果您正在做“典型”的事情，MacPorts 中的版本就足够了。只有当您需要处于最前沿时，您才需要绕过 MacPorts 并手动下载和安装。
It really is easier than doing it manually. For example:
will download, build, and install Gimp, plus all its dependencies. There are a lot of dependencies.
If you're doing "typical" stuff, the versions of stuff in MacPorts will be sufficient. Only if you need to be on the bleeding edge will you need to bypass MacPorts and download and install manually.
虽然 macports 可以使安装更容易，但这是 4 个命令（wget/tar/configure/make）和 1 个命令之间的区别。 macports 真正的亮点在于包管理。如果您主要对 Ruby 开发感兴趣，那么 RubyGems 可能就是您所需要的。如果您正在使用 Ruby on Rails，macports 将对您需要的所有非 Ruby 软件非常有帮助。如果您想完全使用 GUI，您可以使用 Porticus 作为 macports 前端。
我在构建阶段偶尔会遇到问题，但那是在 Tiger 的领导下，它落后于时代了。
While macports can make installation easier, it's the difference between 4 commands (wget/tar/configure/make) and 1 command. Where macports really shines is in package management. If you're primarily interested in Ruby development, RubyGems might be all you need. If you're doing Ruby on Rails, macports will be quite helpful with all the non-ruby software you'll need. If you want to go completely GUI, you can use Porticus as a macports frontend.
I have had the occasional problem during the build phase, but that's under Tiger, which is behind the times.
我更喜欢macports，但有些人喜欢自己做。 Macports 往往落后于发布，但它对我来说仍然有好处
I prefer macports, but some people like doing it themselves. Macports tends to be behind releases, but it's still good for me
macports 最大的问题是它不是跨平台的，并且很难指定一个明确定义的开发场景（例如，您使用 Foo 版本 1.2.3、Bar 版本 0.5.6 等）。它让你的生活变得更轻松，但到目前为止，我仍然没有找到一个像样的解决方案来定义和构建高效、简单和跨平台的开发运行时环境。另请参阅此问题。
所以我的建议是：使用 macports，除非你想非常严格地控制你的开发环境。
The strongest problem with macports is that it's not cross platform, and it's hard to specify a well defined development scenario (e.g. you use Foo version 1.2.3, Bar version 0.5.6 etc.). It makes your life easier, but as of today, I still haven't found a decent solution to the definition and building of a development runtime environment which is efficient, easy and cross platform. See also this question.
So my suggestion is: go with macports, unless you want very strict control of your development environment.
您应该使用包管理器，除非您有明确的、具体的理由不这样做。
当然，我更喜欢fink。
You should use a package manager unless you have a well defined, specific reason not to.
'Course, I prefer fink.