Live data from Hacker News

Hacker's Guide to Setting Up Your Mac

lapwinglabs.com

11–20 of 267 posts

Re: Hacker's Guide to Setting Up Your Mac

#12
post #6

Step 1. Install linux

I get the joke, and it was the first thing that popped in my head too. But in all seriousness, OS X is Unix as well, and can do pretty much any Unix based task that GNU/Linux can. Sometimes the best tool for the job is the one you already own.

Re: Hacker's Guide to Setting Up Your Mac

#13
My stumbling block is always that I start with macports, which requires Xcode, which requires logging into apple, app store, long download, long install ...

Do I understand that brew does not require xcode and I can jump straight from a new machine to `brew install git` (for instance) ?

If so, why does anyone use macports over brew ?

Re: Hacker's Guide to Setting Up Your Mac

#15
post #13

My stumbling block is always that I start with macports, which requires Xcode, which requires logging into apple, app store, long download, long install ... Do I understand that brew does not require xcode and I can jump straight from a new machine to `brew install git` (for instance) ? If so, why does anyone use macports over brew ?

[deleted]

Re: Hacker's Guide to Setting Up Your Mac

#17
post #13

My stumbling block is always that I start with macports, which requires Xcode, which requires logging into apple, app store, long download, long install ... Do I understand that brew does not require xcode and I can jump straight from a new machine to `brew install git` (for instance) ? If so, why does anyone use macports over brew ?

You can download the command line tools directly, you may need to be a registered Apple dev first though

Re: Hacker's Guide to Setting Up Your Mac

#18
post #13

My stumbling block is always that I start with macports, which requires Xcode, which requires logging into apple, app store, long download, long install ... Do I understand that brew does not require xcode and I can jump straight from a new machine to `brew install git` (for instance) ? If so, why does anyone use macports over brew ?

Homebrew also requires at least the OS X Command-line developer tools, which previously were only included with XCode.

I suspect macports might also be able to cope with just these tools? Or does it still have X11 ports?

Re: Hacker's Guide to Setting Up Your Mac

#19

I would also highly suggest installing curl via homebrew. The version that ships with OSX 10.9 has some broken features that might bite you. http://curl.haxx.se/mail/archive-2013-10/0036.html

Did I miss something or does Chrome use the Keychain?

Re: Hacker's Guide to Setting Up Your Mac

#20
post #13

My stumbling block is always that I start with macports, which requires Xcode, which requires logging into apple, app store, long download, long install ... Do I understand that brew does not require xcode and I can jump straight from a new machine to `brew install git` (for instance) ? If so, why does anyone use macports over brew ?

You can download the command line tools directly, you may need to be a registered Apple dev first though

You don't, just run

     xcode-select --install
And it'll prompt you to install the command line tools.
Post reply on HN