I dream of the day when someone properly ports Portage (from Gentoo, the "emerge" thing) to Mac OS X. I use MacPorts, and I've used a bunch of various package management systems, and portage is the only one that lets me maintain servers for > 5 years without reinstalling the whole thing, just upgrading the packages.
Homebrew — MacPorts driving you to drink? Try Homebrew
61–65 of 65 posts
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#62Earlier quoted context omitted.
Why don't you just edit the port to add a variant that lets you opt-out of those dependencies? Poor package management isn't the fault of MacPorts; a Homebrew port could be just as poorly designed. The "variants" infrastructure of MacPorts is one of my favorite parts of MacPorts, it definitely makes it easier to manage interdependencies IMHO.
Truth. Anyone capable of maintaining a homebrew setup has Sufficient skills to spend five minutes scanning the macports guide and tweaking the port files. OTOH, building clojure is te leas of the parents problems; he is in for anworld of painful surprise when he sees how screwed up packaging is. Have a clojure app? Include your own copy of clojure and clojure-contrib. Have a clojure editing mode? Do the same. Have a…
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#63I currently use MacPorts... just wondering why I should switch?
FWIW, I was an early Homebrew user and even contributed a few recipes, but I moved back to MacPorts because (and no offense to mxcl, but it's kind of unavoidable) the author seems to do things with little understanding of the underlying system or justification. Taking ownership of /user/local is completely utterly pointless and just plain bad advice. Copy-and-pasting optimization code from the Gentoo wiki is pointles…
There no good reason I have yet heard why using /usr/local is bad advise. I assume that since you provided no rationale for your statement you are in fact unaware of one.
But anyway having said this it is merely a recommendation — do whatever you want. The installation guide goes to great lengths to tell you that you should do whatever you want.
Back when I initially made Homebrew I was interested in the greatest goal of maximum awesome O99 CFLAG awesomeness. Now I'm only interested in reliable compiles and the default CFLAGS are pretty sensible. At the time I wouldn't have recommended the project to anyone particularly, but it got popular anyway.
But anyway, I never copy and pasted without reading a bunch first. I spent several days researching the stuff, the Gentoo wiki was a good source.
There is no anti MacPorts stuff in any of the docs anymore. I was never anti MacPorts at all, if anyone will believe me. I just found it to be not a great tool for developers. Homebrew is a grass roots project, at the time it seemed harmless fun to poke fun at the competition. As the project became more popular I took it all out. Now there is just a small gibe that I couldn't resist because it's too good a bit of wit.
Finally, no offence? May I suggest next time you say such a thing you don't immediately accuse the person to whom you mean no offence of being both ignorant and arrogant.
PS with offence, you're an ignorant twat, and probably ugly too.
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#64Website need formula -> formulae for pluralization.
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#65Has anyone here tried pkgsrc on OS X?
I used it for a few months but eventually switched over to homebrew because it's a nice simple system and packages most of the stuff I need.
You have to run a case-insensitive filesystem with pkgsrc (I was anyway) and, like macports, it does not use system libraries so pretty much everything needs to be rebuilt under `/usr/pkg`.
It was worth experimenting with. I might check back on it when I get my new MBP. They have [a lot of packages](http://pkgsrc.se/).