I agree with Dave.  Since we're on the anecdote topic, I'll explain
with my own.

Ignoring a bit of time with VMS, I have been a *nix user since the
1980s.  My path has been from BSD to solaris to linux to osx.  A
pleasure in moving from solaris to linux, was the tools for bulding/
install software.  Rpm, yum, apt-get, etc. are very handy when you
just want to get things done and are really not interested in patching
code, or applying patches of questionable provenance.

When I switched to OSX, I thought it would be great to have build/
install tool, and so Fink and Macports were both attractive to me.  I
started with Fink, but something (that I don't recall) annoyed me, so
I switched to Macports.  After a while, though, it too started to wear
thin.

1. Some things were not ported yet.

2. Some ports were not up-to-date.  [Confession: I had ported one of
my own packages (see gri.sf.net) and I didn't even keep that up to
date, partly because it was tiresome having to adjust to slight
changes in the port driver files.]

3. Macports suffers a bit of "dependency hell", as the linux people
call it.  An update to one package can necessitate updates to many
more packages.  (I've done "port" commands that took many hours, just
to update something trivial.)

4. The apple-supplied utilities (compilers and such) are now much more
up to date, so there's no need to use macports to get something
recent.

5. A lot of applications (gui-based software) have been ported
directly to the OSX environment, and are available as self-contained
packages.

Given all of this, I didn't even bother installing macports on the OSX
machines I bought in 2009.  There seemed to be no need at the time.
And, months in, I've not felt any need to install it.  On those rare
occasions when software was not pre-built, I just built it the old-
fashioned way, with ./configure and make.  Very rarely, a patch might
have to be applied, but I'd rather see such things explained on blogs
than trust a patch supplied in a port file.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to