Why doesn’t Mac OS have a standard package manager?
This was final thought Sunday night as I flipped my MacBook shut and stumbled off to bed. I finally got around to configuring my MacBook as my primary development machine this weekend. It’s been 3-4 months since I got my MacBook and I’ve since converted the two other PC’s in my house into Linux machine (Debian and Ubuntu). With that conversion mostly complete it was time to get cracking on making my MacBook into the web development powerhouse for which it was intended. OK, before anyone says anything – it took me 3 months because I had a Lego Star Wars addiction – Don’t judge me!
So after installing Xcode, MacPorts and then Ruby, rubygems and postgresql – I then reconfigured my Eclipse to use the port installed version of Ruby and gems. Which is when I realized that the pre-installed Ruby and gems was not in any way connected to the Mac port installed version. Well, that’s inefficient – I thought.
cialis in usa Women who are breast feeding also should stay away from medicine. The best way is to enquire the couples about their problems and gain a better perceptive order discount viagra to it. With major meals, 1-2 capsulesis enough buy cheap cialis continue reading address for most people. Prostate sildenafil tablets uk http://appalachianmagazine.com/2015/12/30/several-wvu-football-players-ruled-ineligible-for-cactus-bowl-including-worley/ is the biggest sexual gland of men.
Why doesn’t macports just link into what is already installed and go from there? In fact why isn’t macports pre-installed so developers can hit the ground running?
I still think Mac OS is a great platform for development – particularly web apps – but if it came with an integrated package manager it would be awesome.
